Device, Method, and Graphical User Interface for Managing Content Items and Associated Metadata

ABSTRACT

An electronic device: detects, via one or more input devices, a first input that corresponds to selection of a transport affordance while displaying a content item; and, in response to detecting the selection of the transport affordance, displays, on a display, a transport interface provided to perform one or more operations on the content item, including: a tag modification affordance provided to modify tags associated with the content item; and one or more transport option affordances associated with different selectable options for performing the one or more operations on the content item.

RELATED APPLICATION

This application is a continuation application of and claims priority toU.S. patent application Ser. No. 15/978,121, filed on May 12, 2018,which claims priority to U.S. Provisional Patent App. No. 62/506,687,filed on May 16, 2017, which are hereby incorporated by reference intheir entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that enable the management of content items andassociated metadata.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Example touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Example manipulations include adjusting the position and/or size of oneor more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Example user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture, iPhoto, Photos fromApple Inc. of Cupertino, Calif.), a digital content (e.g., videos andmusic) management application (e.g., iTunes from Apple Inc. ofCupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But methods for performing these manipulations are cumbersome andinefficient. For example, using a sequence of mouse based inputs toselect one or more user interface objects and perform one or moreactions on the selected user interface objects is tedious and creates asignificant cognitive burden on a user. In addition, these methods takelonger than necessary, thereby wasting energy. This latter considerationis particularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for managing content items andassociated metadata. Such methods and interfaces optionally complementor replace conventional methods for managing content items andassociated metadata. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated devices, such methods and interfaces conserve powerand increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch-screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer readable storagemedium or other computer program product configured for execution by oneor more processors.

In accordance with some embodiments, a method is performed at a devicewith one or more processors, non-transitory memory, a display, and oneor more input devices. The method includes detecting, via the one ormore input devices, a first input that corresponds to selection of atransport affordance while displaying a content item. The method alsoincludes, in response to detecting the selection of the transportaffordance, displaying, on the display, a transport interface providedto perform one or more operations on the content item, including: a tagmodification affordance provided to modify tags associated with thecontent item; and one or more transport option affordances associatedwith different selectable options for performing the one or moreoperations on the content item.

In accordance with some embodiments, a method is performed at a devicewith one or more processors, non-transitory memory, a display, and oneor more input devices. The method includes: detecting, via the one ormore input devices, a first input that corresponds to selection of acollaboration affordance; and, in response to detecting the selection ofthe collaboration affordance, displaying, on the display, acollaboration interface, including concurrently displaying: arecent-items region that includes a plurality of representations of aplurality of recently modified content items that includes one or morecontent items that are not jointly accessible by other users; and acollaborative-items region that includes a plurality of representationsof a plurality of jointly accessible content items that are jointlyaccessible by the other users.

In accordance with some embodiments, a method is performed at a devicewith one or more processors, non-transitory memory, a display, and oneor more input devices. The method includes: displaying, on the display,a user interface that includes one or more application icons; and, whiledisplaying the user interface, detecting, via the one or more inputdevices, a first input that corresponds to selection of a respectiveapplication icon among the one or more application icons. In response todetecting the selection of the respective application icon, and inaccordance with a determination that the first input satisfies anapplication launch criterion, the method includes launching anapplication associated with the respective application icon. In responseto detecting the selection of the respective application icon, and inaccordance with a determination that the first input satisfies a contentpreview criterion, the method includes displaying, on the display, apreview interface without launching the application, where the previewinterface includes: a plurality of representations of a plurality ofcontent items corresponding to the application associated with therespective application icon; and a plurality of representations of aplurality of tags corresponding to the application associated with therespective application icon.

In accordance with some embodiments, an electronic device includes adisplay, one or more input devices, one or more processors,non-transitory memory, and one or more programs; the one or moreprograms are stored in the non-transitory memory and configured to beexecuted by the one or more processors and the one or more programsinclude instructions for performing or causing performance of theoperations of any of the methods described herein. In accordance withsome embodiments, a non-transitory computer readable storage medium hasstored therein instructions which when executed by one or moreprocessors of an electronic device with a display and one or more inputdevices, cause the device to perform or cause performance of theoperations of any of the methods described herein. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, one or more input devices, a non-transitory memory, andone or more processors configured to execute one or more programs storedin the non-transitory memory, including one or more of the elementsdisplayed in any of the methods described above, which are updated inresponse to inputs, as described in any of the methods described herein.In accordance with some embodiments, an electronic device includes: adisplay, one or more input devices; and means for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, an information processing apparatus,for use in an electronic device with a display and one or more inputdevices, includes means for performing or causing performance of theoperations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface are provided with faster, more efficient methodsand interfaces for managing content items and associated metadata,thereby increasing the effectiveness, efficiency, and user satisfactionwith such devices. Such methods and interfaces may complement or replaceconventional methods for managing content items and associated metadata.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 5A-5H illustrate example user interfaces for managing tags from atransport interface in accordance with some embodiments.

FIGS. 6A-6G illustrate example user interfaces for managing tags from atransport interface in accordance with some embodiments.

FIGS. 6H-6U illustrate example user interfaces for viewing jointlyaccessible content items within a collaboration interface in accordancewith some embodiments.

FIGS. 7A-7P illustrate example user interfaces for previewing contentitems and tags associated with application in accordance with someembodiments.

FIGS. 8A-8C illustrate a flow diagram of a method of managing tags froma transport interface in accordance with some embodiments.

FIGS. 9A-9D illustrate a flow diagram of a method of jointly accessiblecontent items within a collaboration interface in accordance with someembodiments.

FIGS. 10A-10C illustrate a flow diagram of a method of previewingcontent items and tags associated with an application in accordance withsome embodiments.

DESCRIPTION OF EMBODIMENTS

Some applications and/or operating systems enable users to organizefiles and/or documents according to organizational indicators. However,these existing capabilities are often limited to file browserapplications. Accordingly, in embodiments described below, a transportinterface includes regions and/or affordances provided to quickly viewand/or modify tags for an associated content item in order to provide amore seamless and intuitive user experience. In turn, this also reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Some document management applications allow users to collaborate ondocuments. However, these existing document management applicationsoften lack contextual information and/or visibility into other contentitems. Accordingly, in embodiments described below, in order to providea more seamless and intuitive user experience when collaborating oncontent items, a collaboration interface includes: a recent-items regionthat includes a plurality of representations of a plurality of recentlymodified content items that includes one or more content items that arenot jointly accessible by other users; and a collaborative-items regionthat includes a plurality of representations of a plurality of jointlyaccessible content items that are jointly accessible by the other users.This also reduces power usage and improves battery life of the device byenabling the user to use the device more quickly and efficiently.

Typically, when a user selects an application icon, an applicationassociated with the application icon is launched. Alternatively, in someexisting operating systems, when a user hovers over an application icon,a preview of open windows for the application associated with theapplication icon is shown. However, these existing capabilities lackcontextual information and/or visibility into content items for theapplication associated with the application icon. Accordingly, inembodiments described below, after selecting an application icon, apreview interface is displayed without launching the application, wherethe preview interface includes: a plurality of representations of aplurality of content items corresponding to the application associatedwith the respective application icon; and a plurality of representationsof a plurality of tags corresponding to the application associated withthe respective application icon. In turn, the preview interface providesa more seamless and intuitive user experience with additional contextualinformation. This also reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

Below, FIGS. 1A-1B, 2-3, and 4A-4B provide a description of exampledevices. FIGS. 8A-8C illustrate a flow diagram of a method of managingtags from a transport interface. The user interfaces in FIGS. 5A-5H andFIGS. 6A-6G are used to illustrate the process in FIGS. 8A-8C. FIGS.9A-9D illustrate a flow diagram of a method of jointly accessiblecontent items within a collaboration interface. The user interfaces inFIGS. 6H-6U are used to illustrate the process in 9A-9D. FIGS. 10A-10Cillustrate a flow diagram of a method of previewing content items andtags associated with an application. The user interfaces in FIGS. 7A-7Pare used to illustrate the process in 10A-10C.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 163 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an example embodiment, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an example embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch-sensitive display system 112 or an extension of thetouch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 163 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver for obtaining information concerning the location ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 163 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   contacts module 137 (sometimes called an address book or contact    list);-   telephone module 138;-   video conferencing module 139;-   e-mail client module 140;-   instant messaging (IM) module 141;-   workout support module 142;-   camera module 143 for still and/or video images;-   image management module 144;-   browser module 147;-   calendar module 148;-   widget modules 149, which optionally include one or more of: weather    widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm    clock widget 149-4, dictionary widget 149-5, and other widgets    obtained by the user, as well as user-created widgets 149-6;-   widget creator module 150 for making user-created widgets 149-6;-   search module 151;-   video and music player module 152, which is, optionally, made up of    a video player module and a music player module;-   notes module 153;-   map module 154; and/or-   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and video andmusic player module 152, workout support module 142 includes executableinstructions to create workouts (e.g., with time, distance, and/orcalorie burning goals); communicate with workout sensors (in sportsdevices and smart watches); receive workout sensor data; calibratesensors used to monitor a workout; select and play music for a workout;and display, store and transmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wireles sly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In some embodiments includingactive event recognizer determination module 173, event dispatchermodule 174 delivers the event information to an event recognizerdetermined by active event recognizer determination module 173. In someembodiments, event dispatcher module 174 stores in an event queue theevent information, which is retrieved by a respective event receivermodule 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher-level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events ina respective event, such as event 1 (187-1) or event 2 (187-2), include,for example, touch begin, touch end, touch movement, touch cancellation,and multiple touching. In one example, the definition for event 1(187-1) is a double tap on a displayed object. The double tap, forexample, comprises a first touch (touch begin) on the displayed objectfor a predetermined phase, a first lift-off (touch end) for apredetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(187-2) is a dragging on a displayed object. The dragging, for example,comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, the event definition for a respective event, suchas event 1 (187-1) or event 2 (187-2), includes a definition of an eventfor a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event, such asevent 1 (187-1) or event 2 (187-2), also includes delayed actions thatdelay delivery of the event information until after it has beendetermined whether the sequence of sub-events does or does notcorrespond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   Signal strength indicator(s) 402 for wireless communication(s), such    as cellular and Wi-Fi signals;-   Time 404;-   Bluetooth indicator 405;-   Battery status indicator 406;-   Tray 408 with icons for frequently used applications, such as:    -   Icon 416 for telephone module 138, labeled “Phone,” which        optionally includes an indicator 414 of the number of missed        calls or voicemail messages;    -   Icon 418 for e-mail client module 140, labeled “Mail,” which        optionally includes an indicator 410 of the number of unread        e-mails;    -   Icon 420 for browser module 147, labeled “Browser”; and    -   Icon 422 for video and music player module 152, also referred to        as iPod (trademark of Apple Inc.) module 152, labeled “iPod”;        and-   Icons for other applications, such as:    -   Icon 424 for IM module 141, labeled “Text”;    -   Icon 426 for calendar module 148, labeled “Calendar”;    -   Icon 428 for image management module 144, labeled “Photos”;    -   Icon 430 for camera module 143, labeled “Camera”;    -   Icon 432 for online video module 155, labeled “Online Video”;    -   Icon 434 for stocks widget 149-2, labeled “Stocks”;    -   Icon 436 for map module 154, labeled “Map”;    -   Icon 438 for weather widget 149-1, labeled “Weather”;    -   Icon 440 for alarm clock widget 169-6, labeled “Clock”;    -   Icon 442 for workout support module 142, labeled “Workout        Support”;    -   Icon 444 for notes module 153, labeled “Notes”; and    -   Icon 446 for a settings application or module, which provides        access to settings for device 100 and its various applications        136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, in some embodiments, icon 422 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Device 300also, optionally, includes one or more contact intensity sensors (e.g.,one or more of sensors 359) for detecting intensity of contacts ontouch-sensitive surface 451 and/or one or more tactile output generators359 for generating tactile outputs for a user of device 300.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Many of theexamples that follow will be given with reference to a device thatdetects inputs on a touch-sensitive surface that is separate from thedisplay, as shown in FIG. 4B. In some embodiments, the touch-sensitivesurface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B)that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

User Interfaces and Associated Processes

Attention is now directed toward embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as a portable multifunction device (PMD) 100 with adisplay, a touch-sensitive surface, and optionally one or more sensorsto detect intensity of contacts with the touch-sensitive surface, or adevice 300 with one or more processors, non-transitory memory, adisplay, and one or more input devices.

FIGS. 5A-5H illustrate example user interfaces for managing tags from atransport interface in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the process describedbelow, including the processes in FIGS. 8A-8C. Although some of theexamples which follow will be given with reference to inputs on atouch-screen display (where the touch-sensitive surface and the displayare combined), in some embodiments, the device detects inputs on atouch-sensitive surface 451 that is separate from the display 450, asshown in FIG. 4B.

FIG. 5A illustrates displaying a notes interface 502 associated with anotes application executed by the device 100. According to someembodiments, the notes interface 502 is provided to create and/or editcontent items such as notes and reminders. As shown in FIG. 5A, thenotes interface 502 includes: a notes entry region 504 provided to enterand edit the content item (e.g., the note), a toolbar region 506 with aplurality of tool affordances provided to perform operations on thecontent item (e.g., the note), and a transport affordance 508. Forexample, as shown in FIG. 5A, the notes entry region 504 includes a listof items that comprise a note. According to some embodiments, inresponse to activation (e.g., selection with a contact) of the transportaffordance 508, the device 100 displays a transport interface overlaidon the notes interface 502 (e.g., as shown in FIGS. 5A-5B) provided toedit tags associated with the content item (e.g., the note), to sharethe content item (e.g., the note) via one or more communication means(e.g., via email, SMS, etc.), and/or to perform one of a plurality ofoperations on the content item (e.g., the note) such as a copyoperation, a print operation, etc. FIG. 5A also illustrates detecting acontact 510 (e.g., a tap/selection gesture) at a location thatcorresponds to the transport affordance 508.

FIG. 5B illustrates displaying a transport interface 520 over the notesinterface 502 in response to detecting the selection of the transportaffordance 508 in FIG. 5A. According to some embodiments, the transportinterface 520 is provided to modify tags associated with a content item(e.g., the note in FIG. 5A), share the content item (e.g., the note inFIG. 5A), and/or perform an operation on the content item (e.g., thenote in FIG. 5A). In some embodiments, the transport interface 520slides up from the bottom edge of the display area of the device 100.

As shown in FIG. 5B, the transport interface 520 includes: a tags region521, a local sharing affordance 515 provided to share the content item(e.g., the note in FIG. 5A) with one or more users (not shown) via alocal interface (e.g., BLUETOOTH, NFC, WiFi, and/or the like) inresponse to selection thereof (e.g., with a tap/selection gesture),sharing affordances 512 a, 512 b, 512 c, and 512 d (sometimescollectively referred to herein as the “sharing affordances 512”)provided to share the content item (e.g., the note in FIG. 5A) viacorresponding communication means (e.g., SMS, email, cloud storage, andothers) in response to selection thereof (e.g., with a tap/selectiongesture), operation affordances 514 a, 514 b, 514 c, and 514 d(sometimes collectively referred to herein as the “operation affordances514”) provided to perform corresponding operations on the content item(e.g., the note in FIG. 5A) in response to selection thereof (e.g., witha tap/selection gesture), and a cancel affordance 516 provided todismiss the transport interface 520 in response to selection thereof(e.g., with a tap/selection gesture).

As shown in FIG. 5B, the tags region 521 includes a thumbnail image 522of the content item (e.g., the note in FIG. 5A) and metadata 524associated with the content item (e.g., the name, location, modificationdate, creation date, creator's name, and/or the like of the note in FIG.5A). As shown in FIG. 5B, the tags region 521 also includes tags 526 aand 526 b that are currently associated with the content item (e.g., thenote in FIG. 5A) and a tag modification affordance 528 provided tomodify (e.g., remove, add, and/or edit) tags associated with the contentitem (e.g., the note in FIG. 5A) in response to selection thereof (e.g.,with a tap/selection gesture).

In FIG. 5B, the tag 526 a corresponds to a “Hawaii” category, and thetag 526 b corresponds to a “Lists” category. According to someembodiments, each tag corresponds to a category or subject in order toorganize content items such as notes, documents, files, images, media,and the like. According to some embodiments, each tag is associated witha color, pattern, and/or appearance in order to organize content itemssuch as notes, documents, files, images, media, and the like. In someembodiments, each tag is associated with a unique color, pattern, and/orappearance.

FIGS. 5B-5F show a sequence in which an association between a contentitem (e.g., the note) and a tag is added (e.g., an operation thatassociates a tag with the content item). FIG. 5B also illustratesdetecting a contact 518 (e.g., a tap/selection gesture) at a locationthat corresponds to the tag modification affordance 528. FIG. 5Cillustrates replacing display of the transport interface 520 with a tagmodification interface 530 provided to modify tags associated with thecontent item (e.g., the note) in response to detecting the selection ofthe modification affordance 528 in FIG. 5B.

As shown in FIG. 5C, the tag modification interface 530 includes: thetags region 521 (e.g., similar to and adapted from the tags region 521within the transport interface 520 in FIG. 5B), a tag creation field 534provided to display a tag creation interface 540 in response toselection thereof (e.g., with a tap/selection gesture as shown in FIG.5C-5D), and the cancel affordance 516 provided to dismiss the tagmodification interface 530 in response to selection thereof (e.g., witha tap/selection gesture). As shown in FIG. 5C, the tag modificationinterface 530 also includes a plurality of selectable tags 532 a, 532 b,532 c, 532 d (sometimes collectively referred to herein as the“selectable tags 532”). In FIG. 5C, a first subset of the selectabletags 532 corresponds to tags that are currently associated with thecontent item (e.g., the selectable tags 532 a and 532 b) as indicated bythe indicators 535 (e.g., the check mark icons), and a second subset ofthe selectable tags 532 corresponds to suggested tags (e.g., theselectable tags 532 c and 532 d) based on frequency of use, recency ofuse, and/or the like.

FIG. 5C also illustrates detecting a contact 552 (e.g., a tap/selectiongesture) at a location that corresponds to the tag creation field 534.FIG. 5D illustrates replacing display of the tag modification interface530 with a tag creation interface 540 provided to create a new tag andassociate a content item (e.g., the note in FIG. 5A) with the new tag inresponse to detecting the selection of the tag creation field 534 inFIG. 5C. As shown in FIG. 5D, the tag creation interface 540 includes:the tags region 521 (e.g., similar to and adapted from the tags region521 within the transport interface 520 in FIG. 5B), an input field 542provided to create a name or category for a new tag, and a plurality ofselectable tag appearance affordances 546 a, 546 b, 546 c, 546 d, 546 e,and 546 f (sometimes collectively referred to herein as the “tagappearance affordances 546”) provided to select a color, pattern, and/orappearance for the new tag. According to some embodiments, the inputfield 542 is provided to receive one or more characters input via thesoftware (SW) keyboard 545, a hardware keyboard, a speech-to-textapplication, and/or the like.

As shown in FIG. 5D, the tag creation interface 540 also includes: acancel affordance 544 a provided to dismiss the tag creation interface540 in response to detecting the selection thereof (e.g., with atap/selection gesture), and an “add tag” affordance 544 b provided toassociate the new tag with a content item (e.g., the note in FIG. 5A) inresponse to detecting the selection thereof (e.g., with a tap/selectiongesture as shown in FIG. 5E-5F). For example, as shown in FIG. 5D, atext string “Summer” is displayed within the input field 542 in responseto detecting a sequence of inputs entering the associated characters viathe software keyboard 545 (not shown).

FIG. 5D also illustrates detecting a contact 554 (e.g., a tap/selectiongesture) at a location that corresponds to the tag appearance affordance546 b. FIG. 5E illustrates displaying a check mark within the tagappearance affordance 546 b to indicate that the color, pattern, and/orappearance associated with the tag appearance affordance 546 b isassociated with the new tag in response to detecting the selection ofthe tag appearance affordance 546 b in FIG. 5D.

FIG. 5E also illustrates detecting a contact 556 (e.g., a tap/selectiongesture) at a location that corresponds to the “add tag” affordance 544b. FIG. 5F illustrates replacing display of the tag creation interface540 with the tag modification interface 530 in response to detecting theselection of the “add tag” affordance 544 b in FIG. 5E. FIG. 5F alsoillustrates displaying the new selectable tag 532 e within the tagmodification interface 530 in response to detecting the selection of the“add tag” affordance 544 b in FIG. 5E. As shown in FIG. 5F, the contentitem (e.g., the note in FIG. 5A) is currently associated with the newselectable tag 532 e (e.g., created in FIGS. 5D-5F) as indicated by theindicator 535 (e.g., a check mark icon). As shown in FIG. 5F, the tagsregion 521 has been updated to remove the tags 526 a and 526 b and todisplay the tags representation 529 indicating that the content item(e.g., the note in FIG. 5A) is now associated with three tags (e.g., the“Hawaii,” “Lists,” and “Summer” categories). According to someembodiments, the tags 526 a and 526 b have been replaced with therepresentation 529 due to a dimensional constraint of the tags region521 (e.g., a width limit).

FIGS. 5F-5G show a sequence in which an association between the contentitem (e.g., the note) and a tag is removed (e.g., an operation thatdissociates a tag with the content item). FIG. 5F also illustratesdetecting a contact 558 (e.g., a tap/selection gesture) at a locationthat corresponds to the selectable tag 532 b (e.g., associated with the“Lists” category). FIG. 5G illustrates removing the indicator 535associated with the selectable tag 532 b to indicate that the associatedtag (e.g., “Lists”) is no longer associated with the content item (e.g.,the note) in response to detecting the selection of the selectable tag532 b in FIG. 5F. As shown in FIG. 5G, the tags region 521 has beenupdated to remove the representation 529 and to display the tags 526 aand 526 c indicating that the content item (e.g., the note in FIG. 5A)is now associated with two tags (e.g., the “Hawaii” and “Summer”categories).

FIGS. 5G-5H show another sequence in which an association between thecontent item (e.g., the note) and another tag is removed (e.g., anoperation that dissociates another tag with the content item). FIG. 5Galso illustrates detecting a contact 560 (e.g., a tap/selection gesture)at a location that corresponds to the tag 526 c (e.g., associated withthe “Summer” category). FIG. 5H illustrates removing the indicator 535associated with the selectable tag 532 e to indicate that the associatedtag (e.g., Summer) is no longer associated with the content item (e.g.,the note) in response to detecting the selection of the tag 526 c inFIG. 5G. As shown in FIG. 5H, the tags region 521 has been updated toremove the tag 526 c in order to indicate that the note is nowassociated with one tag (e.g., the “Hawaii” category).

FIGS. 6A-6G illustrate example user interfaces for managing tags from atransport interface in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the process describedbelow, including the processes in FIGS. 8A-8C. FIGS. 6H-6U illustrateexample user interfaces for jointly accessible content items within acollaboration interface in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the process describedbelow, including the processes in FIGS. 9A-9D. Although some of theexamples which follow will be given with reference to inputs on atouch-screen display (where the touch-sensitive surface and the displayare combined), in some embodiments, the device detects inputs on atouch-sensitive surface 451 that is separate from the display 450, asshown in FIG. 4B.

FIG. 6A illustrates displaying a presentation creation interface 600associated with a presentation creation application executed by thedevice 100. According to some embodiments, the presentation creationinterface 600 is provided to create and/or edit content items such asslide-decks, slideshows, presentations, and/or the like. As shown inFIG. 6A, the presentation creation interface 600 includes: a toolbarregion 602 with a plurality of tool affordances provided to performoperations on the content item (e.g., the slide-deck, slideshow, orpresentation), a content preview region 604 with a plurality ofrepresentations of sub-items (e.g., slides) that comprise the contentitem, and a content entry region 606 associated with a current sub-item(e.g., a respective slide). As shown in FIG. 6A, the toolbar region 602includes a transport affordance 608.

According to some embodiments, in response to activation (e.g.,selection with a contact) of the transport affordance 608, the device100 displays a transport interface overlaid on the presentation creationinterface 600 (e.g., as shown in FIGS. 6A-6B) provided to edit tagsassociated with the content item (e.g., the presentation), to share thecontent item (e.g., the presentation) via one or more communicationmeans (e.g., via email, SMS, etc.), and/or to perform one of a pluralityof operations on the content item (e.g., the presentation) such as acopy operation, a print operation, etc. FIG. 6A also illustratesdetecting a contact 610 (e.g., a tap/selection gesture) at a locationthat corresponds to the transport affordance 608.

FIG. 6B illustrates displaying a transport interface 620 over thepresentation creation interface 600 in response to detecting theselection of the transport affordance 608 in FIG. 6A. According to someembodiments, the transport interface 620 is provided to modify tagsassociated with a content item and/or perform an operation on thecontent item. As shown in FIG. 6B, the transport interface includes: atags region 621, a local sharing affordance 615 provided to share thecontent item (e.g., the presentation in FIG. 6A) with one or more users(not shown) via a local interface (e.g., BLUETOOTH, NFC, WiFi, and/orthe like) in response to selection thereof (e.g., with a tap/selectiongesture), sharing affordances 612 a, 612 b, 612 c, and 612 d (sometimescollectively referred to herein as the “sharing affordances 612”)provided to share the content item (e.g., the presentation in FIG. 6A)via corresponding communication means (e.g., SMS, email, cloud storage,and others) in response to selection thereof (e.g., with a tap/selectiongesture), and operation affordances 614 a, 614 b, 614 c, and 614 d(sometimes collectively referred to herein as the “operation affordances614”) provided to perform corresponding operations on the content item(e.g., the presentation in FIG. 6A) in response to selection thereof(e.g., with a tap/selection gesture).

As shown in FIG. 6B, the tags region 621 includes a thumbnail image 622of the content item (e.g., the presentation in FIG. 6A) and metadata 624associated with the content item (e.g., the name, size, location,modification date, creation date, creator's name, and/or the like of thepresentation in FIG. 6A). As shown in FIG. 6B, the tags region 621 alsoincludes a tag modification affordance 628 provided to modify (e.g.,remove, add, and/or edit) tags associated with the content item (e.g.,the presentation in FIG. 6A) in response to selection thereof (e.g.,with a tap/selection gesture).

FIGS. 6B-6F show a sequence in which an association between a contentitem (e.g., the presentation in FIG. 6A) and a tag is added (e.g., anoperation that associates a tag with the content item). FIG. 6B alsoillustrates detecting a contact 627 (e.g., a tap/selection gesture) at alocation that corresponds to the tag modification affordance 628. FIG.6C illustrates replacing display of the transport interface 620 with atag modification interface 630 provided to modify tags associated withthe content item (e.g., the presentation in FIG. 6A) in response todetecting the selection of the modification affordance 628 in FIG. 6B.

As shown in FIG. 6C, the tag modification interface 630 includes: thetags region 621 (e.g., similar to and adapted from the tags region 621in the transport interface 620 in FIG. 6B), and a tag creation field 634provided to display a tag creation interface 640 in response toselection thereof (e.g., with a tap/selection gesture as shown in FIG.6C-6D). As shown in FIG. 6C, the tag modification interface 630 alsoincludes a plurality of selectable tags 632 a, 632 b, 632 c, 632 d(sometimes collectively referred to herein as the “selectable tags632”). In FIG. 6C, the content item (e.g., the presentation in FIG. 6A)is not currently associated with any tags. As such, in FIG. 6C, theselectable tags 632 a, 632 b, 632 c, 632 d correspond to suggested tagsbased on frequency of use, recency of use, and/or the like.

FIG. 6C also illustrates detecting a contact 633 (e.g., a tap/selectiongesture) at a location that corresponds to the tag creation field 634.FIG. 6D illustrates replacing display of the tag modification interface630 with a tag creation interface 640 provided to create a new tag andassociate the content item (e.g., the presentation in FIG. 6A) with thenew tag in response to detecting the selection of the tag creation field634 in FIG. 6C.

As shown in FIG. 6D, the tag creation interface 640 includes: the tagsregion 621 (e.g., similar to and adapted from the tags region 621 withinthe transport interface 620 in FIG. 6B), an input field 642 provided tocreate a name or category for a new tag, a plurality of selectable tagappearance affordances 646 a, 646 b, 646 c, 646 d, 646 e, and 646 f(sometimes collectively referred to herein as the “tag appearanceaffordances 646”) provided to select a color, pattern, and/or appearancefor the new tag. According to some embodiments, the input field 642 isprovided to receive one or more characters input via a softwarekeyboard, a hardware keyboard, a speech-to-text application, and/or thelike. As shown in FIG. 6D, the tag creation interface 640 also includes:a cancel affordance 644 a provided to dismiss the tag creation interface640 in response to detecting the selection thereof (e.g., with atap/selection gesture), and an “add tag” affordance 644 b provided toassociate the new tag with a content item (e.g., the presentation inFIG. 6A) in response to detecting the selection thereof (e.g., with atap/selection gesture as shown in FIG. 6E-6F).

FIG. 6E illustrates displaying a text string “Brainstorming” within theinput field 642 in response to detecting a sequence of inputs enteringthe associated characters via a software keyboard (not shown). FIG. 6Ealso illustrates displaying a check mark within the tag appearanceaffordance 646 a to indicate that the color, pattern, and/or appearanceassociated with the tag appearance affordance 646 a is associated withthe new tag in response to detecting the selection of the tag appearanceaffordance 646 a (not shown).

FIG. 6E further illustrates detecting a contact 645 (e.g., atap/selection gesture) at a location that corresponds to the “add tag”affordance 644 b. FIG. 6F illustrates replacing display of the tagcreation interface 640 with the tag modification interface 630 inresponse to detecting the selection of the “add tag” affordance 644 b inFIG. 6E. FIG. 6F also illustrates displaying the new selectable tag 632e within the tag modification interface 630 in response to detecting theselection of the “add tag” affordance 644 b in FIG. 6E. As shown in FIG.6F, the content item (e.g., the presentation in FIG. 6A) is currentlyassociated with the new selectable tag 632 e (e.g., created in FIGS.6D-6E) as indicated by the indicator 635 (e.g., a check mark icon). Asshown in FIG. 6F, the tags region 621 has been updated to show the tag626 a indicating that the content item (e.g., the presentation in FIG.6A) is now associated with a tag (e.g., the “Brainstorming” category).

FIGS. 6F-6H show a sequence in which the presentation creation interfaceis replaced with a content item browsing interface. FIG. 6F alsoillustrates detecting a contact 647 (e.g., a tap/selection gesture) at alocation that corresponds to the tag 626 a. FIG. 6G illustratesdisplaying an option menu 650 in response to detecting the selection ofthe tag 626 a in FIG. 6F. As shown in FIG. 6G, the option menu 650includes: a “remove tag” affordance 652 a provided to remove theassociation between the content item (e.g., the presentation in FIG. 6A)and the tag 626 a in response to selection thereof (e.g., with atap/selection gesture), and a “show all files with tag” affordance 652 bprovided to display a content items browsing interface 660 that showscontent items associated with the tag 626 a in response to selectionthereof (e.g., with a tap/selection gesture as shown in FIG. 6G-6H).

FIG. 6G also illustrates detecting a contact 649 (e.g., a tap/selectiongesture) at a location that corresponds to the “show all files with tag”affordance 652 b. FIG. 6H illustrates displaying the content itemsbrowsing interface 660 in response to detecting the selection of the“show all files with tag” affordance 652 b in FIG. 6G. As shown in FIG.6H, the content items browsing interface 660 includes: a search bar 654provided to search for and display resulting content items, a primaryregion 656, a collaboration view affordance 658 a provided to display acollaboration interface 680 in response to selection thereof (e.g., witha tap/selection gesture as shown in FIG. 6K-6L), a projects viewaffordance 658 b provided to display a projects interface 6130 inresponse to selection thereof (e.g., with a tap/selection gesture asshown in FIG. 6S-6T), and a browser view affordance 658 c provided todisplay the content item browsing interface 660 in response to selectionthereof (e.g., with a tap/selection gesture).

As shown in FIG. 6H, the content items browsing interface 660 alsoincludes a filter sidebar with a plurality of selectable filter options,including: a locations region 659 a with a plurality of selectablefilter affordances 662 a, 662 b, 662 c, and 662 d that correspond tostorage locations (e.g., cloud storage services, local storage devices,remote storage devices, and/or attached/peripheral storage devices suchas USB devices); a favorites region 659 b with a plurality of selectablefilter affordances 664 a, 664 b, and 664 c that correspond to favoritefolders or directories (e.g., folder A through C); and tags region 659 cwith a plurality of selectable filter affordances 668 a, 668 b, 668 c,668 d, 668 e, and 668 f (sometimes collectively referred to herein asthe “tag filter affordances 668”) that correspond to tags associatedwith content items aggregated across storage locations.

According to some embodiments, each of the tag filter affordances 668 isassociated with a tag that corresponds to a category or subject in orderto organize content items such as notes, documents, files, images,media, and the like. According to some embodiments, each of the tagfilter affordances 668 is associated with a tag that corresponds to acolor, pattern, and/or appearance in order to organize content itemssuch as notes, documents, files, images, media, and the like. In someembodiments, each tag is associated with a unique color, pattern, and/orappearance.

As shown in FIG. 6H, the selectable filter affordance 668 a associatedwith the “Brainstorming” tag is currently selected as indicated by theindicator 665 (e.g., a check mark icon). In FIG. 6H, the primary region656 includes a content item representation 661 for a content item thatis associated with the “Brainstorming” tag. For example, the contentitem representation 661 corresponds to the presentation in FIG. 6A. Insome embodiments, the content item representations in the primary region656 correspond to icons indicating a file type of the associated contentitems. In some embodiments, the content item representations in theprimary region 656 correspond to thumbnail images/previews of theassociated content items. In some embodiments, metadata associated withcorresponding content items is displayed proximate to each of thecontent item representations in the primary region 656. For example, themetadata includes the name, size, location, modification date, creationdate, creator's name, and/or the like for the associated content items.In some embodiments, the content item representations in the primaryregion 656 include a text description.

FIGS. 6H-6I show a sequence in which the content item representationsdisplayed within the content item browsing interface are filtered basedon selected tag(s). FIG. 6H also illustrates detecting a contact 667(e.g., a tap/selection gesture) at a location that corresponds to theselectable filter affordance 668 a (e.g., the “Brainstorming” tag). FIG.61 illustrates removing display of the content item representation 661within the primary region 656 in response to detecting the selection ofthe selectable filter affordance 668 a in FIG. 6H. For example, thecontent item (e.g., the presentation in FIG. 6A) that corresponds to thecontent item representation 661 is associated with the now-unselectedselectable filter affordance 668 a (e.g., the “Brainstorming” tag). Inthis example, no content item representations are displayed within theprimary region 656 because none of the selectable filter affordances arecurrently selected in FIG. 6I.

FIGS. 6I-6J show another sequence in which the content itemrepresentations displayed within the content item browsing interface arefurther filtered based on selected tag(s). FIG. 6I also illustratesdetecting a contact 669 (e.g., a tap/selection gesture) at a locationthat corresponds to the selectable filter affordance 668 b (e.g.,associated with the “Motorcycles” tag). FIG. 6J illustrates displayingcontent item representations 672 a, 672 b, 672 c, 672 d, and 672 e(sometimes collectively referred to herein as the “representations 672”)within the primary region 656 in response to detecting the selection ofthe selectable filter affordance 668 b in FIG. 6I. For example, thecontent items that correspond to the representations 672 are associatedwith the now-selected selectable filter affordance 668 b (e.g., the“Motorcycles” tag). As shown in FIG. 6J, the selectable filteraffordance 668 b associated with the “Motorcycles” tag is currentlyselected as indicated by the indicator 665 (e.g., a check mark icon).

FIGS. 6J-6K show yet another sequence in which the content itemrepresentations displayed within the content item browsing interface arefurther filtered based on selected tag(s). FIG. 6J also illustratesdetecting a contact 671 (e.g., a tap/selection gesture) at a locationthat corresponds to the selectable filter affordance 668 c (e.g.,associated with the “Leather Jackets” tag). FIG. 6K illustratesdisplaying content item representations 674 a, 674 b, 674 c, 674 d, 674e, and 674 f (sometimes collectively referred to herein as the“representations 674”) within the primary region 656 in response todetecting the selection of the selectable filter affordance 668 c inFIG. 6J. For example, the content items that correspond to therepresentations 674 are associated with the now-selected selectablefilter affordance 668 c (e.g., the “Leather Jackets” tag). As shown inFIG. 6K, the selectable filter affordance 668 c associated with the“Leather Jackets” tag is currently selected as indicated by theindicator 665 (e.g., a check mark icon).

As shown in FIG. 6K, the primary region 656 is sorted such that a firstsubset 675 a of the representations 672 and 674 (e.g., the content itemrepresentations 672 a, 672 b, 672 c, 674 a, and 674 b) that correspondto content items associated with both the “Motorcycles” tag and the“Leather Jackets” tag is displayed at the top of the primary region 656.As shown in FIG. 6K, a second subset 675 b of the representations 672and 674 (e.g., the content item representations 672 d, 672 e, 674 c, 674d, 674 e, and 674 f) that correspond to content items associated withone of the “Motorcycles” tag or the “Leather Jackets” tag (but not both)are displayed below the first subset 675 a within the primary region656.

FIGS. 6K-6L show a sequence in which the content item browsing interfaceis replaced with a collaboration interface. FIG. 6K also illustratesdetecting a contact 673 (e.g., a tap/selection gesture) at a locationthat corresponds to the collaboration view affordance 658 a. FIG. 6Lillustrates replacing display of the content items browsing interface660 with the collaboration interface 680 in response to detecting theselection of the collaboration view affordance 658 a in FIG. 6K. Asshown in FIG. 6L, the collaboration interface 680 includes: arecent-items region 682 with a plurality of representations of aplurality of recently modified content items, and a collaborative-itemsregion 692 with a plurality of representations of a plurality of jointlyaccessible content items that are jointly accessible by other users.According to some embodiments, the recent-items region 682 includesrepresentations of one or more content items that are not jointlyaccessible by the other users.

As shown in FIG. 6L, the recent-items region 682 includes content itemrepresentations (CI Reps) 684 a, 684 b, 684 c, 684 d, 684 e, 684 f, 684g, 684 h, 684 i, 684 j, 684 k, 684 l, 684 m, and 684 n (sometimescollectively referred to herein as the “representations 684”) andassociated metadata 686 a, 686 b, 686 c, 686 d, 686 e, 686 f, 686 g, 686h, 686 i, 686 j, 686 k, 686 l, 686 m, and 686 n. For example, themetadata includes the name, size, location, modification date, creationdate, creator's name, and/or the like for the associated content item.In FIG. 6L, the recent-items region 682 also includes a “See more”affordance 688 provided to see additional representations of theplurality of recently modified content items in response to selectionthereof (e.g., with a tap/selection gesture).

As shown in FIG. 6L, the collaborative-items region 692 includes contentitem representations (CI Reps) 694 a, 694 b, 694 c, 694 d, 694 e, 694 f,and 694 g (sometimes collectively referred to herein as the“representations 694”) and associated metadata 696 a, 696 b, 696 c, 696d, 696 e, 696 f, and 696 g. For example, the metadata includes the name,size, location, modification date, creation date, creator's name, and/orthe like for the associated content item. In FIG. 6L, thecollaborative-items region 692 also includes a “See more” affordance 698provided to see additional representations of the plurality of jointlyaccessible content items in response to selection thereof (e.g., with atap/selection gesture).

In some embodiments, the representations 684 and 694 correspond to iconsindicating a file type of the associated content items. In someembodiments, the representations 684 and 694 correspond to thumbnailimages/previews of the associated content items. In some embodiments,metadata associated with corresponding content items is displayedproximate to each of the representations 684 and 694.

FIGS. 6L-6M show a sequence in which a content preview interface isoverlaid on the collaboration interface. FIG. 6L also illustratesdetecting a contact 681 (e.g., a tap/selection gesture) at a locationthat corresponds to the content item representation 684 j. FIG. 6Millustrates displaying a content preview interface 685 in response todetecting the selection of the content item representation 684 j in FIG.6L. As shown in FIG. 6M, the content preview interface 685 correspondsto the content item associated with the content item representation 684j.

FIGS. 6M-6N show a sequence in which the collaboration interface isscrolled in a vertical direction. FIG. 6M also illustrates detecting afirst scrolling gesture (e.g., a swipe or tap-and-drag gesture) with acontact 683 in a first direction (e.g., vertical) within thecollaboration interface 680. FIG. 6N illustrates scrolling thecollaboration interface 680 in a downward direction in response todetecting the first scrolling gesture in FIG. 6M. As shown in FIG. 6N,the collaboration interface 680 includes a projects region 6102 and acollaborators region 6112.

As shown in FIG. 6N, the projects region 6102 includes a plurality ofselectable tags 6104 a, 6104 b 6104 c, 6104 d, 6104 e, and 6104 f(sometimes collectively referred to herein as the “tags 6104”).According to some embodiments, in response to selection of one of thetags 6104, and in accordance with a determination that the selectioninput satisfies first criteria (e.g., tap gesture, etc.), the device 100filters the representations 684 shown in the recent-items region 682 andthe representations 694 shown in the collaborative-items region 692 toinclude representations for content items associated with the selectedtag (e.g., as shown in FIGS. 6O-6P). According to some embodiments, inresponse to selection of one of the tags 6104, and in accordance with adetermination that the selection input satisfies second criteria (e.g.,a double-tap gesture, long press gesture, deep press gesture, etc.), thedevice 100 replaces display of the collaboration interface 680 with theprojects interface 6130.

According to some embodiments, the tags 6104 are associated with thecontent items that correspond to the representations 684 and 694. Inanother example, the tags 6104 correspond to frequently used tags,recently used tags, and/or the like. According to some embodiments, eachof the tags 6104 corresponds to a category or subject. According to someembodiments, each of the tags 6104 is associated with a color, pattern,and/or appearance. In some embodiments, each of the tags 6104 isassociated with a unique color, pattern, and/or appearance.

As shown in FIG. 6N, the collaborators region 6112 includes selectablecollaborator representations 6114 a, 6114 b 6114 c, 6114 d, 6114 e, 6114f, 6114 g, and 6114 h (sometimes collectively referred to herein as the“collaborator representations 6114”). In some embodiments, each of thecollaborator representations 6114 corresponds to person with access tothe content items that correspond to the representations 694 within thecollaborative-items region 692. For example, a project supervisorauthorizes and/or invites users to work and collaborate on a project. Inthis example, the authorized/invited users are given read and/or writeaccess to the jointly accessible content items that correspond to therepresentations 694 within the collaborative-items region 692. In someembodiments, each of the collaborator representations 6114 includes animage, avatar, or portrait of a corresponding collaborator. In someembodiments, metadata is displayed proximate to each of the collaboratorrepresentations 6114. For example, the metadata includes the associatedcollaborator's name, title, access privileges, phone number, emailaddress, residential address, office location, availability, and/or thelike.

According to some embodiments, in response to selection of one of thecollaborator representations 6114, and in accordance with adetermination that the selection input satisfies first criteria (e.g.,tap gesture, etc.), the device 100 filters the representations 684 shownin the recent-items region 682 and the representations 694 shown in thecollaborative-items region 692 to include representations for contentitems associated with the selected collaborator (e.g., as shown in FIGS.6P-6Q). According to some embodiments, in response to selection of oneof the collaborator representations 6114, and in accordance with adetermination that the selection input satisfies second criteria (e.g.,a double-tap gesture, long press gesture, deep press gesture, etc.), thedevice 100 displays a user information interface 6115 that correspond tothe selected collaborator overlaid on the collaboration interface 680(e.g., as shown in FIGS. 6Q-6R).

FIGS. 6N-6O show a sequence in which the collaborative-items region ofthe collaboration interface is scrolled in a horizontal direction. FIG.6N also illustrates detecting a second scrolling gesture (e.g., a swipeor tap-and-drag gesture) with a contact 687 in a second direction (e.g.,horizontal) within the collaborative-items region 692. FIG. 6Oillustrates scrolling the collaborative-items region 692 in aright-to-left direction in response to detecting the second scrollinggesture in FIG. 6N. As shown in FIG. 6O, the collaborative-items region692 has been updated to show a portion of a content item representation694 h and associated metadata 696h.

FIGS. 6O-6P show a sequence in which the content item representationsdisplayed within the collaborative-items region of the collaborationinterface are filtered based on selected tag(s). FIG. 60 alsoillustrates detecting a contact 689 (e.g., a tap/selection gesture) at alocation that corresponds to the “Finance” tag 6104 f. FIG. 6Pillustrates filtering the representations 684 shown in the recent-itemsregion 682 and the representations 694 shown in the collaborative-itemsregion 692 to include representations for content items associated withthe “Finance” tag 6104 f in response to detecting the selection of the“Finance” tag 6104 f in FIG. 60 that satisfies the first criteria. Asshown in FIG. 6P, the collaborative-items region 692 has been updated toinclude content item representations 694 b, 694 c, 694 d, and 694 e.

FIGS. 6P-6Q show a sequence in which the content item representationsdisplayed within the collaborative-items region of the collaborationinterface are further filtered based on selected collaborator(s). FIG.6P also illustrates detecting a contact 691 (e.g., a tap/selectiongesture) at a location that corresponds to the collaboratorrepresentation 6114 h. FIG. 6Q illustrates filtering the representations684 shown in the recent-items region 682 and the representations 694shown in the collaborative-items region 692 to include representationsfor content items associated with the “Finance” tag 6104 f and thecollaborator representation 6114 h in response to detecting theselection of the “collaborator representation 6114 h in FIG. 6P thatsatisfies the first criteria.

As shown in FIG. 6Q, the collaborative-items region 692 has been updatedto include content item representations 694 b and 694 c. According tosome embodiments, the collaborative-items region 692 is updated to showcontent item representations for content items that match both the“Finance” tag 6104 f and the collaborator representation 6114 h.According to some embodiments, the collaborative-items region 692 isupdated to show content item representations for content items thatmatch the “Finance” tag 6104 f or the collaborator representation 6114h. According to some embodiments, the collaborative-items region 692 isupdated to show content item representations for content items thatmatch the “Finance” tag 6104 f and/or the collaborator representation6114 h.

FIGS. 6Q-6R show a sequence in which a user information interface isoverlaid on the collaboration interface. FIG. 6Q also illustratesdetecting a contact 693 (e.g., a tap/selection gesture) at a locationthat corresponds to the collaborator representation 6114 c. FIG. 6Rillustrates displaying a user information interface 6115 overlaid on thecollaboration interface 680 in response to detecting the selection ofthe collaborator representation 6114 c in FIG. 6Q that satisfies thesecond criteria. As shown in FIG. 6R, the user information interface6115 includes user information for a respective collaborator thatcorrespond to the collaborator representation 6114 c. For example, theuser information includes metadata such as the name, title, accessdetails, phone number, email address, residential address, officelocation, availability, and/or the like for the respective collaborator.

FIGS. 6R-6S show another sequence in which the collaboration interfaceis scrolled in a vertical direction. FIG. 6R also illustrates detectinga third scrolling gesture (e.g., a swipe or tap-and-drag gesture) with acontact 695 in the first direction (e.g., vertical) within thecollaboration interface 680. FIG. 6S illustrates scrolling thecollaboration interface 680 in a downward direction in response todetecting the third scrolling gesture in FIG. 6R. As shown in FIG. 6S,the collaboration interface 680 includes a locations region 6122. InFIG. 6S, the locations region 6122 includes storage locationrepresentations 6124 a, 6124 b, 6124 c, and 6124 d (sometimescollectively referred to herein as the “location representations 6124”)and associated metadata 6126 a, 6126 b, 6126 c, and 6126 d for differentstorage locations (e.g., cloud storage services, local storage devices,remote storage devices, and/or attached/peripheral storage devices suchas USB devices). For example, the associated metadata includes anindication of access privileges, total capacity, free space, uptime,storage device name, storage device type, and/or the like.

FIGS. 6S-6T show a sequence in which the collaboration interface isreplaced with a projects interface. FIG. 6S also illustrates detecting acontact 697 (e.g., a tap/selection gesture) at a location thatcorresponds to the projects view affordance 658 b. FIG. 6T illustratesreplacing display of the collaboration interface 680 with the projectsinterface 6130 in response to detecting the selection of the projectsview affordance 658 b in FIG. 6S. As shown in FIG. 6T, the projectsinterface 6130 includes: a first project region 6142 a associated withthe “Brainstorming” tag 6104 a, a second project region 6142 bassociated with the “Motorcycles” tag 6104 b, and a third project region6142 c associated with the “Leather Jackets” tag 6104 c.

In FIG. 6T, the first project region 6142 a includes content itemrepresentations 6132 a, 6132 b, 6132 c, 6132 d, 6132 e, and 6132 f andassociated metadata 6134 a, 6134 a, 6134 c, 6134 d, 6134 e, and 6134 fthat correspond to content items associated with the “Brainstorming” tag6104 a. In FIG. 6T, the second project region 6142 b includes contentitem representations 672 a, 672 b, 672 c, 672 d, and 672 e (sometimescollectively referred to herein as the “representations 672”) andassociated metadata 676 a, 676 b, 676 c, 676 d, and 676 e thatcorrespond to content items associated with the “Motorcycles” tag 6104 b(e.g., similar to representations 672 shown in FIG. 6J). For example,the metadata includes the name, size, location, modification date,creation date, creator's name, and/or the like for the associatedcontent items.

FIGS. 6T-6U show a sequence in which the projects interface is replacedwith the content item browsing interface. FIG. 6T also illustratesdetecting a contact 6131 (e.g., a tap/selection gesture) at a locationthat corresponds to the “Motorcycles” tag 6104 b within the projectsinterface 6130. FIG. 6U illustrates replacing display of the projectsinterface 6130 with the content items browsing interface 660 in responseto detecting the selection of the “Motorcycles” tag 6104 b in FIG. 6T.The content items browsing interface 660 in FIG. 6U is similar to andadapted from the content items browsing interface 660 in FIG. 6J. Assuch, FIG. 6J and FIG. 6U include similar user interfaces and elementslabeled with the same reference number in both figures have the samefunction, with only the differences described herein for the sake ofbrevity. As shown in FIG. 6U, the primary region 656 includes therepresentations 672 for the content items associated with the“Motorcycles” tag. As shown in FIG. 6U, the selectable filter affordance668 b associated with the “Motorcycles” tag is currently selected asindicated by the indicator 665 (e.g., a check mark icon).

FIGS. 7A-7P illustrate example user interfaces for previewing contentitems and tags associated with an application in accordance with someembodiments. The user interfaces in these figures are used to illustratethe process described below, including the processes in FIGS. 10A-10C.Although some of the examples which follow will be given with referenceto inputs on a touch-screen display (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface 451 that is separate from thedisplay 450, as shown in FIG. 4B.

FIG. 7A illustrates displaying a home screen interface 700 associatedwith the operating system (OS) executed by the device 100. According tosome embodiments, the home screen interface 700 is a startup, default,or landing interface. As shown in FIG. 7A, the home screen interface 700includes a plurality of application icons 702 a, 702 b, 702 c, 702 d,702 e, 702 f, 702 g, and 702 h (sometimes collectively referred toherein as the “application icons 702”) for a plurality of applications(e.g., productivity application, media consumption applications, mediacreation application, finance application, games, workout application,communication applications, social media application, and/or the like)and a dock region 704 with a plurality of application icons 706 a, 706b, 706 c, 706 d, 706 e, and 706 f (sometimes collectively referred toherein as the “application icons 706”) for a plurality of applications(e.g., a file browser application, a music application, a wordprocessing application, a spreadsheet application, a presentationapplication, a PDF viewer application, and/or the like). According tosome embodiments, the application icons 702 and 706 are usercustomizable.

According to some embodiments, in response to detecting an input thatcorresponds to selecting an application icon, and in accordance with adetermination that the input satisfies an application launch criterion(e.g., a click input, tap input, or the like), the device 100 launchesthe application associated with the selected application icon by, forexample, displaying an interface or window associated with theapplication. According to some embodiments, in response to detecting aninput that corresponds to selecting an application icon, and inaccordance with a determination that the input satisfies a contentpreview criterion (e.g., a hover input, double click input, double tapinput, long press input, deep press input, or the like), the device 100display a preview interface for the application that corresponds to theapplication icon over the current interface.

FIGS. 7A-7B show a sequence in which a preview interface is displayedover a home screen in response to detecting selection of an applicationicon within a dock region. FIG. 7A also illustrates detecting a contact711 (e.g., a tap/selection gesture) at a location that corresponds tothe application icon 706 a within the dock region 704. FIG. 7Billustrates displaying a preview interface 710 for the file browserapplication that corresponds to the application icon 706 a in responseto detecting the selection of the application icon 706 a in FIG. 7A thatsatisfies the content preview criterion.

As shown in FIG. 7B, the preview interface 710 for the file browserapplication includes a plurality of content item representations 714 a,714 b, 714 c, 714 d, 714 e, and 714 f (sometimes collectively referredto herein as the “representations 714”) for content items (e.g.,presentations/slide-decks, notes, emails, images, messages, wordprocessing documents, spreadsheets, audio files, videos, electronicdocuments, and/or the like). In another example, the representations 714correspond to frequently viewed and/or modified content items, recentlyviewed and/or modified content items, and/or the like. As shown in FIG.7B, the preview interface 710 for the file browser application alsoincludes a plurality of tag representations 708 a, 708 b, and 708 c(sometimes collectively referred to herein as the “representations 708”)for tags.

For example, the representations 708 correspond to tags that areassociated with the content items that correspond to the representations714. In another example, the representations 708 correspond tofrequently used tags, recently used tags, and/or the like. According tosome embodiments, each of the representations 708 is associated with atag that corresponds to a category or subject. According to someembodiments, each of the representations 708 is associated with a tagthat corresponds to a color, pattern, and/or appearance. For example,each of the associated tags has a unique color, pattern, and/orappearance. As shown in FIG. 7B, the preview interface 710 for the filebrowser application further includes a “see more” affordance 712provided to launch the file browser application in response to selectionthereof (e.g., with a tap/selection gesture).

FIGS. 7B-7D show a sequence in which a respective application islaunched in response to detecting a drag-and-drop gesture where acontent item representation is dragged out of the preview interface anddropped over an application icon associated with the respectiveapplication. FIG. 7B also illustrates detecting a drag-and-drop gesturewith a contact 711 according to motion vector 713 where the content itemrepresentation 714 f (e.g., associated with an image) is dragged out ofthe preview interface 710 for the file browser application and droppedover the application icon 702 h. FIG. 7C illustrates displaying thecontent item representation 714 f over the application icon 702 h priorto lift-off of the contact 711.

FIG. 7D illustrates displaying a presentation creation interface 730 inresponse to the drag-and-drop gesture in FIGS. 7B-7C that resulted indropping the content item representation 714 f over the application icon702 h. In some embodiments, the presentation creation interface 730 isassociated with a presentation creation application executed by thedevice 100. According to some embodiments, the presentation creationinterface 730 is provided to create and/or edit content items such asslide-decks, slideshows, presentations, and/or the like. As shown inFIG. 7D, the presentation creation interface 730 includes: a toolbarregion 732 with a plurality of tool affordances provided to performoperations on the content item (e.g., the slide-deck, slideshow, orpresentation), a content preview region 734 with a plurality ofrepresentations of sub-items (e.g., slides) that comprise the contentitem, and a content entry region 736 associated with a current sub-item(e.g., a respective slide). As shown in FIG. 7D, the content entryregion 736 includes a content item 715 (e.g., an image) that correspondsto the content item representation 714 f in FIGS. 7B-7C.

FIGS. 7E-7F show another sequence in which a preview interface isdisplayed over a home screen in response to detecting selection ofanother application icon within the dock region. The home screeninterface 700 in FIG. 7E is similar to and adapted from the home screeninterface 700 in FIG. 7A. As such, FIG. 7A and FIG. 7E include similaruser interfaces and elements labeled with the same reference number inboth figures have the same function, with only the differences describedherein for the sake of brevity. FIG. 7E illustrates detecting a contact721 (e.g., a tap/selection gesture) at a location that corresponds tothe application icon 706 f within the dock region 704. FIG. 7Fillustrates displaying a preview interface 740 for the PDF viewerapplication that corresponds to the application icon 706 f in responseto detecting the selection of the application icon 706 f in FIG. 7E thatsatisfies the content preview criterion.

As shown in FIG. 7F, the preview interface 740 for the PDF viewerapplication includes a plurality of content item representations 746 a,746 b, 746 c, 746 d, 746 e, and 746 f (sometimes collectively referredto herein as the “representations 746”) for content items (e.g.,electronic documents) associated with the PDF view application. Forexample, the representations 746 are sorted based on how frequentlyand/or recently the associated content items have been viewed and/ormodified. As shown in FIG. 7F, the preview interface 740 for the PDFviewer application also includes a plurality of tag representations 744a, 744 b, and 744 c (sometimes collectively referred to herein as the“representations 744”) for tags.

For example, the representations 744 correspond to tags that areassociated with the content items that corresponds to therepresentations 746. In another example, the representations 746correspond to frequently used tags, recently used tags, and/or the like.According to some embodiments, each of the representations 744 isassociated with a tag that corresponds to a category or subject.According to some embodiments, each of the representations 744 isassociated with a tag that corresponds to a color, pattern, and/orappearance. For example, each of the associated tags has a unique color,pattern, and/or appearance. As shown in FIG. 7F, the preview interface740 for the PDF viewer application further includes a “see more”affordance 742 provided to launch the PDF viewer application in responseto selection thereof (e.g., with a tap/selection gesture).

FIGS. 7F-7G show a sequence in which a preview interface is displayedover the home screen in response to detecting selection of anapplication icon outside the dock region. FIG. 7F also illustratesdetecting a contact 723 (e.g., a tap/selection gesture) at a locationthat corresponds to the application icon 702 f outside of the dockregion 704. FIG. 7G illustrates displaying a preview interface 750 forthe application (e.g., application ABC) that corresponds to theapplication icon 702 f in response to detecting the selection of theapplication icon 702 f in FIG. 7F that satisfies the content previewcriterion.

As shown in FIG. 7G, the preview interface 750 includes a plurality ofcontent item representations 756 a, 756 b, 756 c, 756 d, 756 e, 756 f,756 g, and 756 h (sometimes collectively referred to herein as the“representations 756”) for content items associated with the application(e.g., application ABC). For example, the representations 756 are sortedbased on how frequently and/or recently the associated content itemshave been viewed and/or modified. As shown in FIG. 7G, the previewinterface 750 also includes a plurality of tag representations 754 a,754 b, and 754 c (sometimes collectively referred to herein as the“representations 754”) for tags.

For example, the representations 754 correspond to tags that areassociated with the content items that correspond to the representations756. In another example, the representations 754 correspond tofrequently used tags, recently used tags, and/or the like. According tosome embodiments, each of the representations 754 is associated with atag that corresponds to a category or subject. According to someembodiments, each of the representations 754 is associated with a tagthat corresponds to a color, pattern, and/or appearance. For example,each of the associated tags has a unique color, pattern, and/orappearance. As shown in FIG. 7G, the preview interface 750 furtherincludes a “see more” affordance 752 provided to launch the application(e.g., application ABC) in response to selection thereof (e.g., with atap/selection gesture).

FIGS. 7G-7H show a sequence in which a portion of the preview interfaceis scrolled in a vertical direction. FIG. 7G also illustrates detectinga first scrolling gesture (e.g., a swipe or tap-and-drag gesture) with acontact 731 in a first direction (e.g., vertical) within a second region758 b of the preview interface 750 that includes the representations756. FIG. 7H illustrates scrolling the second region 758 b of thepreview interface 750 that includes the representations 756 in adownward direction in response to detecting the first scrolling gesturein FIG. 7G.

FIGS. 7H-7I show a sequence in which a portion of the preview interfaceis scrolled in a horizontal direction. FIG. 7H also illustratesdetecting a second scrolling gesture (e.g., a swipe or tap-and-draggesture) with a contact 733 in a second direction (e.g., horizontal)within a first region 758 a of the preview interface 750 that includesthe representations 754. FIG. 71 illustrates scrolling the first region758 a of the preview interface 750 that includes the representations 754in a right-to-left direction in response to detecting the secondscrolling gesture in FIG. 7H.

FIGS. 7I-7J show a sequence in which an application is launched inresponse to detecting selection of a corresponding an application iconwithin the dock region. FIG. 7I also illustrates detecting a contact 735(e.g., a double tap, long press, or deep press gesture) at a locationthat corresponds to the application icon 706 e within the dock region704. FIG. 7J illustrates displaying the presentation creation interface730 for the presentation creation application that corresponds to theapplication icon 706 e in response to detecting the selection of theapplication icon 706 e in FIG. 7I that satisfies the application launchcriterion. The presentation creation interface 730 in FIG. 7J is similarto and adapted from the presentation creation interface 730 in FIG. 7D.As such, FIG. 7D and FIG. 7J include similar user interfaces andelements labeled with the same reference number in both figures have thesame function, with only the differences described herein for the sakeof brevity.

According to some embodiments, in response to detecting an input thatcorresponds to selecting an application icon, and in accordance with adetermination that the input satisfies an application launch criterion(e.g., a click input, tap input, or the like), the device 100 launchesthe application associated with the selected application icon by, forexample, displaying an interface or window associated with theapplication. According to some embodiments, in response to detecting aninput that corresponds to selecting an application icon, and inaccordance with a determination that the input satisfies a contentpreview criterion (e.g., a hover input, double click input, double tapinput, long press input, deep press input, or the like), the device 100display a preview interface for the application that corresponds to theapplication icon over the current interface.

FIGS. 7J-7K show a sequence in which a quick access dock region isoverlaid on an application interface. FIG. 7J also illustrates detectinga predefined gesture (e.g., a swipe or tap-and-drag gesture) with acontact 741 from a bottom edge of the display area in an upwarddirection. For example, the predefined gesture from the bottom edge ofthe display area in the upward direction corresponds to displaying adock region over the current interface. FIG. 7K illustrates displaying adock region 745 (sometimes also referred to herein as the “quick accessdock region 745”) in response to detecting the predefined gesture fromthe bottom edge of the display area in the upward direction in FIG. 7J.For example, the dock region 745 slides up from the bottom edge of thedisplay area.

As shown in FIG. 7K, the dock region 745 includes a plurality ofapplication icons 706 a, 706 b, 706 c, 706 d, 706 e, and 706 f(sometimes collectively referred to herein as the “application icons706”) for a plurality of applications (e.g., a file browser application,a music application, a word processing application, a spreadsheetapplication, a presentation application, a PDF viewer application,and/or the like). According to some embodiments, the application icons706 within the dock region 745 are user customizable.

FIGS. 7K-7L show a sequence in which a preview interface is displayedover the application interface in response to detecting selection of anapplication icon within the dock region. FIG. 7K also illustratesdetecting a contact 743 (e.g., a tap/selection gesture) at a locationthat corresponds to the application icon 706 f within the dock region745. FIG. 7L illustrates displaying the preview interface 740 for thePDF viewer application that corresponds to the application icon 706 fover the presentation creation interface 730 in response to detectingthe selection of the application icon 706 f in FIG. 7K that satisfiesthe content preview criterion. The preview interface 740 in FIG. 7L issimilar to and adapted from the preview interface 740 in FIG. 7F. Assuch, FIG. 7F and FIG. 7L include similar user interfaces and elementslabeled with the same reference number in both figures have the samefunction, with only the differences described herein for the sake ofbrevity.

FIGS. 7L-7M show another sequence in which a preview interface isdisplayed over the application interface in response to detectingselection of another application icon within the dock region. FIG. 7Lalso illustrates detecting a contact 751 (e.g., a tap/selection gesture)at a location that corresponds to the application icon 706 a within thedock region 745. FIG. 7M illustrates displaying the preview interface710 for the file browser application that corresponds to the applicationicon 706 a over the presentation creation interface 730 in response todetecting the selection of the application icon 706 a in FIG. 7L thatsatisfies the content preview criterion. The preview interface 710 inFIG. 7M is similar to and adapted from the preview interface 710 in FIG.7B. As such, FIG. 7B and FIG. 7M include similar user interfaces andelements labeled with the same reference number in both figures have thesame function, with only the differences described herein for the sakeof brevity.

FIGS. 7M-7N show a sequence in which a content item is added to theapplication interface in response to detecting a drag-and-drop gesturewhere a content item representation is dragged out of the previewinterface and dropped over the application interface. FIG. 7M alsoillustrates detecting a drag-and-drop gesture with a contact 753according to motion vector 755 where the content item representation 714a (e.g., associated with an image) is dragged out of the previewinterface 710 for the file browser application and dropped over into thecontent entry region 736 within the presentation creation interface 730.FIG. 7N illustrates displaying a content item 775 (e.g., an image) thatcorresponds to the content item representation 714 a within the contententry region 736 in response to detecting the drag-and-drop gesture inFIG. 7M.

FIGS. 7N-7O show a sequence in which the content item representationswithin the preview interface are filtered in response to a firstfiltering operation. FIG. 7N also illustrates detecting a contact 757(e.g., a tap/selection gesture) at a location that corresponds to thetag representation 708 b (e.g., associated with the “Learning” tag)within the preview interface 710 (e.g., the first filtering operation).FIG. 7O illustrates filtering the representations 714 within the previewinterface 710 in response to the first filtering operation in FIG. 7N.As shown in FIG. 70, the representations 714 displayed within thepreview interface 710 are filtered to include the content itemrepresentations 714 a, 714 b, 714 c, and 714 d for the content itemsthat are associated with the “Learning” tag.

FIGS. 7O-7P show another sequence in which the content itemrepresentations within the preview interface are further filtered inresponse to a second filtering operation. FIG. 70 also illustratesdetecting a contact 759 (e.g., a tap/selection gesture) at a locationthat corresponds to the tag representation 708 c (e.g., associated withthe “Study” tag) within the preview interface 710 (e.g., the secondfiltering operation). FIG. 7P illustrates filtering the representations714 within the preview interface 710 in response to the second filteringoperation in FIG. 7O. As shown in FIG. 7P, the representations 714displayed within the preview interface 710 are further filtered toinclude the content item representations 714 a and 714 b for the contentitems that are associated with the “Learning” tag and the “Study” tag.

According to some embodiments, the preview interface 710 is updated toshow content item representations for content items that match both the“Learning” tag and the “Study” tag. According to some embodiments, thepreview interface 710 is updated to show content item representationsfor content items that match the “Learning” tag or the “Study” tag.According to some embodiments, the preview interface 710 is updated toshow content item representations for content items that match the“Learning” tag and/or the “Study” tag.

FIGS. 8A-8C illustrate a flow diagram of a method 800 of managing tagsfrom a transport interface in accordance with some embodiments. Themethod 800 is performed at an electronic device (e.g., the portablemultifunction device 100 in FIG. 1A, or the device 300 in FIG. 3) with adisplay, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface. In someembodiments, the display is a touch-screen display and the one or moreinput devices is on or integrated with the display (e.g., the device isa tablet or smartphone). In some embodiments, the display is separatefrom the one or more input devices (e.g., the device is a laptop with aseparate display and touchpad, or desktop computer with a separatedisplay and mouse). Some operations in method 800 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, the method 800 provides an intuitive way to managetags from a transport interface. The method reduces the cognitive burdenon a user when managing tags from a transport interface, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to manage tags from a transportinterface faster and more efficiently conserves power and increases thetime between battery charges.

While displaying a content item (e.g., a presentation/slide-deck, note,email, image, message, word processing document, spreadsheet, audiofile, video, electronic document, or the like), the device detects(802), via the one or more input devices, a first input that correspondsto selection of a transport affordance. As one example, in FIG. 5A,while the displaying a note within a notes interface 502 associated witha notes application, the device 100 detects a contact 510 selecting thetransport affordance 508. As another example, in FIG. 6A, while thedisplaying a presentation (or a respective slide thereof) within apresentation creation interface 600 associated with a presentationcreation application, the device 100 detects a contact 610 selecting thetransport affordance 608.

In response to detecting the selection of the transport affordance, thedevice (804) displays, on the display, a transport interface (e.g., ashare sheet displayed as a pop-over panel, pane, window, etc.) providedto perform one or more operations on the content item, including: a tagmodification affordance provided to modify tags associated with thecontent item; and one or more transport option affordances (e.g.,sharing affordances and/or operation affordances) associated withdifferent selectable options for performing the one or more operationson the content item. In some embodiments, the transport affordancescorrespond to exporting the content item to another application, copyingthe content item, duplicating the content item, saving the content item,pushing the content item to a smart TV (e.g., AppleTV), archiving thecontent item, moving the content item to a different directory/folder,printing the content item, collaborating with others on the contentitem, sharing the content item (e.g., via SMS, email, social mediaplatforms, a local interface (AirDrop), etc.), and/or the like.According to some embodiments, the tag modification affordance withinthe transport interface provides a seamless user experience thatrequires less time and user inputs when modifying tags associated with acontent item, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

As one example, in response to detecting the selection of the transportaffordance 508 in FIG. 5A, the device 100 displays a transport interface520 over the notes interface 502 in FIG. 5B. As shown in FIG. 5B, thetransport interface 520 includes: a plurality of sharing affordances 512provided to share the content item (e.g., the note in FIG. 5A) viacorresponding communication means (e.g., SMS, email, cloud storage, andothers); and a plurality of operation affordances 514 provided toperform corresponding operations on the content item (e.g., the note inFIG. 5A). As shown in FIG. 5B, the transport interface 520 also includesa tags region 521 with a thumbnail image 522 of the content item (e.g.,the note in FIG. 5A) and metadata 524 associated with the content item(e.g., the name, location, modification date, creation date, creator'sname, and/or the like of the note in FIG. 5A). As shown in FIG. 5B, thetags region 521 also includes: tags 526 a and 526 b that are currentlyassociated with the content item (e.g., the note in FIG. 5A), and a tagmodification affordance 528 provided to modify (e.g., remove, add,and/or edit) tags associated with the content item (e.g., the note) inresponse to selection thereof (e.g., with a tap/selection gesture).

As another example, in response to detecting the selection of thetransport affordance 608 in FIG. 6A, the device 100 displays a transportinterface 620 over the presentation creation interface 600 in FIG. 6B.As shown in FIG. 6B, the transport interface 620 includes: a pluralityof sharing affordances 612 provided to share the content item (e.g., thepresentation in FIG. 6A) via corresponding communication means (e.g.,SMS, email, cloud storage, and others); and a plurality of operationaffordances 614 provided to perform corresponding operations on thecontent item (e.g., the presentation in FIG. 6A). As shown in FIG. 6B,the transport interface 620 also includes a tags region 621 with athumbnail image 622 of the content item (e.g., the presentation in FIG.6A) and metadata 624 associated with the content item (e.g., the name,location, modification date, creation date, creator's name, and/or thelike of the presentation in FIG. 6A). As shown in FIG. 6B, the tagsregion 621 also includes a tag modification affordance 628 provided tomodify (e.g., remove, add, and/or edit) tags associated with the contentitem (e.g., the presentation in FIG. 6A) in response to selectionthereof (e.g., with a tap/selection gesture).

In some embodiments, the transport interface includes (806) anindication of one or more nearby users with which the content item canbe shared. As one example, in FIG. 5B, the transport interface 520includes a local sharing affordance 515 provided to share the contentitem (e.g., the note in FIG. 5A) with one or more users (not shown) viaa local interface (e.g., BLUETOOTH, NFC, WiFi, and/or the like). Asanother example, in FIG. 6B, the transport interface 620 includes alocal sharing affordance 615 provided to share the content item (e.g.,the presentation in FIG. 6A) with one or more users (not shown) via alocal interface (e.g., BLUETOOTH, NFC, WiFi, and/or the like).

In some embodiments, the transport interface includes (808) anindication of one or more tags currently associated with the contentitem. According to some embodiments, the indication of the tagscurrently associated a content item within the transport interfaceprovides a seamless user experience that requires less time and userinputs when viewing and modifying tags associated with the content item,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

As one example, in FIG. 5B, the tags region 521 of the transportinterface 520 includes tags 526 a and 526 b that are currentlyassociated with the content item (e.g., the note in FIG. 5A). In FIG.5B, the tag 526 a corresponds to a “Hawaii” category, and the tag 526 bcorresponds to a “Lists” category. According to some embodiments, eachtag corresponds to a category or subject in order to organize contentitems such as notes, documents, files, images, media, and the like.According to some embodiments, each tag is associated with a color,pattern, and/or appearance in order to organize content items such asnotes, documents, files, images, media, and the like. In someembodiments, each tag is associated with a unique color, pattern, and/orappearance.

In some embodiments, displaying the transport interface that includesthe indication of one or more tags currently associated with the contentitem includes (810): in accordance with a determination that a dimension(e.g., a width dimension) of the indication of the one or more tagscurrently associated with the content item satisfies a predefineddimensional constraint of the transport interface, displaying theindication of the one or more tags currently associated with the contentitem includes displaying expanded representations of the one or moretags currently associated with the content item, and, in accordance witha determination that the dimension of the indication of the one or moretags currently associated with the content item does not satisfy thepredefined dimensional constraint of the transport interface, displayingthe indication of the one or more tags currently associated with thecontent item includes displaying collapsed representations of the one ormore tags currently associated with the content items. According to someembodiments, the expanded and collapsed representations of the tagscurrently associated a content item within the transport interfaceprovide a seamless user experience that requires less time and userinputs when viewing and modifying tags associated with the content item,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

As one example, in FIG. 5B, the device 100 displays the tags 526 a and526 b within the tags region 521 in accordance with a determination thata dimension of the tags 526 a and 526 b (e.g., a sum of pixelscorresponding to the width of the tags 526 a and 526 b) satisfies apredefined dimensional constraint of the transport interface (e.g., apredetermined pixel limit). As another example, in FIG. 5F, the device100 displays the tags representation 529 (e.g., a collapsedrepresentation of the tags 526 a, 526 b, and 526 c) within the tagsregion 521 in accordance with a determination that a dimension of thetags 526 a, 526 b, and 526 c (e.g., a sum of pixels corresponding to thewidth of the tags 526 a, 526 b, and 526 c) does not satisfy thepredefined dimensional constraint of the transport interface (e.g., thepredetermined pixel limit).

In some embodiments, the device (812): detects, via the one or moreinput devices, a second input that corresponds to selection of the tagmodification affordance (e.g., tap or click on the tag modificationaffordance); and, in response to detecting the selection of the tagmodification affordance, replaces display of the transport interfacewith a tag modification interface (e.g., a pop-over menu, panel, pane,window, etc.) that includes at least one of: one or more selectable tagscurrently associated with the content item; and one or more selectablesuggested tags. According to some embodiments, the tag modificationinterface provides a seamless user experience that requires less timeand user inputs when viewing and modifying tags associated with thecontent item, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, each of the one or more existing tags and the oneor more suggested tags in the tag modification interface are associatedwith a unique color/appearance scheme in order to easily differentiatethe tags. In some embodiments, the tag modification affordance alsoincludes a content item region that includes a thumbnail image of thecontent item and metadata associated with the content item. In someembodiments, the one or more existing tags and the one or more suggestedtags are displayed in separate regions. In some embodiments, the one ormore existing tags and the one or more suggested tags are displayed inthe same region.

As one example, in response to detecting the selection of the tagmodification affordance 528 with the contact 518 in FIG. 5B, the device100 replaces display of the transport interface 520 with a tagmodification interface 530 in FIG. 5C. As shown in FIG. 5C, the tagmodification interface 530 includes a plurality of selectable tags 532with first subset that corresponds to tags that are currently associatedwith the note (e.g., the selectable tags 532 a and 532 b) as indicatedby the indicators 535 (e.g., check mark icons), and a second subset thatcorresponds to suggested tags (e.g., the selectable tags 532 c and 532d) based on frequency of use, recency of use, and/or the like. As shownin FIG. 5C, the tag modification interface 530 also includes the tagsregion 521 (e.g., similar to and adapted from the tags region 521 withinthe transport interface 520 in FIG. 5B) and a tag creation field 534provided to display a tag creation interface 540 in response toselection thereof (e.g., with a tap/selection gesture as shown in FIG.5C-5D).

In some embodiments, the one or more selectable suggested tags areselected (814) based on at least one of: frequency of use, recency ofuse, or contextual information associated with the content item. In someembodiments, the one or more selectable suggested tags also include theexisting tags with indicator icons (e.g., check mark icons). Forexample, as shown in FIG. 5C, a second subset of the selectable tags 532corresponds to suggested tags (e.g., the selectable tags 532 c and 532d) based on frequency of use, recency of use, and/or the like.

In some embodiments, the tag modification interface also includes (816)a user-modifiable tag creation field provided to create a new tag to beassociated with the content item. For example, as shown in FIG. 5C, thetag modification interface 530 includes a tag creation field 534provided to display a tag creation interface 540 in response toselection thereof (e.g., with a tap/selection gesture as shown in FIG.5C-5D). According to some embodiments, the user-modifiable tag creationfield provides a seamless user experience that requires less time anduser inputs when adding a new association between a tag and a contentitem, which, additionally, reduces power usage and improves battery lifeof the device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device (818): detects, via the one or moreinput devices, a third input that corresponds to selection of arespective tag among the one or more selectable tags currentlyassociated with the content item (e.g., tap or click on the existingtag); and, in response to detecting the selection of the respective tag,removes the association between the respective tag and the content item.According to some embodiments, the ability to remove an associationbetween a tag and a content from within the tag modification interfaceprovides a seamless user experience that requires less time and userinputs when modifying tags associated with the content item, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device automatically dissociates the respectivetag without further user inputs. In some embodiments, the devicedisplays indicator icons (e.g., check mark icons) proximate to the oneor more existing tags. In some embodiments, in response to detecting theselection of the respective tag, the device ceases to display therespective tag within the tag modification interface. As one example,FIGS. 5G-5H show a sequence in which the device 100 removes anassociation between the content item (e.g., the note) and the tag 526 cin response to selection of the tag 526 c within the tags region 521 ofthe tag modification interface 530.

In some embodiments, in response to detecting the selection of therespective tag, the device displays (820), on the display, an optionmenu that includes a first affordance (e.g., removal affordance)provided to remove the association between the respective tag and thecontent item when selected and a second affordance (e.g., “see more” or“see all” affordance) provided to display representations of one or morecontent items associated with the respective tag when selected, wherethe one or more content items include the content item. For example, theoption menu corresponds to a quick action pop-over menu overlaid on thetag modification interface. In some embodiment, a file browserapplication is launched and displayed, in response to selection of thesecond affordance, where the file browser application aggregates contentitems across multiple applications/sources that include the selectedexisting tag. According to some embodiments, the option menu provides aseamless user experience that requires less time and user inputs whenmodifying tags associated with the content item, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

As one example, FIGS. 6F-6G show a sequence in which the device 100displays an option menu 650 associated with the tag 626 a in response toselection of the tag 626 a within the tags region 621 of the tagmodification interface 630. As shown in FIG. 6G, the option menu 650includes a “remove tag” affordance 652 a provided to remove theassociation between the content item (e.g., the presentation in FIG. 6A)and the tag 626 a in response to selection thereof (e.g., with atap/selection gesture), and a “show all files with tag” affordance 652 bprovided to display a content items browsing interface 660 that showscontent items associated with the tag 626 a in response to selectionthereof (e.g., with a tap/selection gesture as shown in FIG. 6G-6H).

In some embodiments, the device (822): detects, via the one or moreinput devices, a fourth input that corresponds to selection of arespective selectable suggested tag among the one or more selectablesuggested tags (e.g., tap or click on the existing tag); and, inresponse to detecting the selection of the respective selectablesuggested tag, associates the respective selectable suggested tag withthe content item and displays, on the display, the respective selectablesuggested tag among the one or more tags currently associated with thecontent item. According to some embodiments, the ability to add anassociation between a tag and a content item from within the tagmodification interface provides a seamless user experience that requiresless time and user inputs when modifying tags associated with thecontent item, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, in response to detecting the selection of therespective selectable suggested tag, the device displays an indicatoricon proximate to the respective selectable suggested tag. As oneexample, with reference to FIG. 5C, in response to selection of theselectable tag 532 c (not shown), the device 100 associates tag 532 c(e.g., “Music”) with the content item (e.g., the note in FIG. 5A) andalso displays an associated tag indicator within the tags regions 521 ofthe tag modification interface 530 and an indicator 535 (e.g., a checkmark indicator) proximate to the tag 532 c.

In some embodiments, the device (824): detects, via the one or moreinput devices, a sequence of one or more inputs that corresponds toinputting a string of one or more characters for a new tag within thetag creation field and completing the string for the new tag; and, inresponse to detecting completion of the string of one or more charactersfor the new tag: associates the new tag with the content item; anddisplays, on the display, the new tag among the one or more tagscurrently associated with the content item. According to someembodiments, the user-modifiable tag creation field provides a seamlessuser experience that requires less time and user inputs when adding anew association between a tag and a content item, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

For example, the sequence of one or more inputs corresponds to speakingcharacters of a word or phrase for a new tag. In another example, thesequence of one or more inputs corresponds to entering characters of aword or phrase for a new tag via a software keyboard, a physicalkeyboard, or the like. As one example, FIGS. 5C-5F show a sequence inwhich a new tag (e.g., “Summer” associated with selectable tag 532 e andthe tag 526 c) is created by entering an associated text string withinthe creation interface 540 via a software keyboard 545 and the new tagis associated with the content item (e.g., the note in FIG. 5A).

In some embodiments, the device (826): detects, via the one or moreinput devices, a fourth input that corresponds to selection of arespective tag among the one or more tags currently associated with thecontent item (e.g., tap or click on the existing tag); and, in responseto detecting the selection of the respective tag, displays, on thedisplay, an option menu that includes a first affordance (e.g., removalaffordance) provided to dissociate the respective tag with the contentitem when selected and a second affordance (e.g., a “see more” or “seeall” affordance) provided to display representations of one or morecontent items associated with the respective tag, where the one or morecontent items include the content item. According to some embodiments,the option menu provides a seamless user experience that requires lesstime and user inputs when modifying tags associated with the contentitem, which, additionally, reduces power usage and improves battery lifeof the device by enabling the user to use the device more quickly andefficiently.

For example, the option menu corresponds to a quick action pop-over menuoverlaid on the transport interface. For example, the option menu issimilar to or adapted from the option menu 650 in FIG. 6G. In someembodiment, a file browser application is launched and displayed, inresponse to selection of the second affordance, where the file browserapplication aggregates content items across multipleapplications/sources that include the selected existing tag.

As one example, with reference to FIG. 5B, in response to selection ofthe tag 526 a within the tags region 521 of the transport interface 520(not shown), the device 100 displays an option menu (e.g., similar tothe option menu 650 in FIG. 6G). In this example, the option menuincludes a “remove tag” affordance provided to remove the associationbetween the content item (e.g., the note in FIG. 5A) and the tag 526 ain response to selection thereof (e.g., with a tap/selection gesture),and a “show all files with tag” affordance provided to display a contentitems browsing interface that shows content items associated with thetag 526 a in response to selection thereof (e.g., with a tap/selectiongesture.

In some embodiments, the device (828): detects, via the one or moreinput devices, a fifth input that corresponds to selection of arespective transport option affordance among the one or more transportoption affordances (e.g., tap or click on the existing tag); and, inresponse to detecting the selection of the respective transport optionaffordance: in accordance with a determination that the respectivetransport option affordance corresponds to sharing the content item viaa first application, causes the content item to be shared via the firstapplication; and, in accordance with a determination that the respectivetransport option affordance corresponds to sharing the content item viaa second application different from the first application, causes thecontent item to be shared via the second application.

As one example, with reference to FIG. 5B, in response to selection ofthe sharing affordance 512 a within the transport interface 520 (notshown), the device 100 causes the content item (e.g., the note in FIG.5A) to be shared by a first application that corresponds to the sharingaffordance 512 a (e.g., a text messaging or SMS application). As anotherexample, with reference to FIG. 5B, in response to selection of thesharing affordance 512 b within the transport interface 520 (not shown),the device 100 causes the content item (e.g., the note in FIG. 5A) to beshared by a second application that corresponds to the sharingaffordance 512 b (e.g., an email application).

As yet another example, with reference to FIG. 5B, in response toselection of the operation affordance 514 a within the transportinterface 520 (not shown), the device 100 causes a first operation thatcorresponds to the operation affordance 514 a (e.g., a copy operation)to be performed on the content item (e.g., the note in FIG. 5A). As yetanother example, with reference to FIG. 5B, in response to selection ofthe operation affordance 514 c within the transport interface 520 (notshown), the device 100 causes a second operation that corresponds to theoperation affordance 514 c (e.g., a print operation) to be performed onthe content item (e.g., the note in FIG. 5A).

It should be understood that the particular order in which theoperations in FIGS. 8A-8C have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,the methods 900 and 1000) are also applicable in an analogous manner tomethod 800 described above with respect to FIGS. 8A-8C. For example, thetransport interfaces, tag modification affordances, transport optionaffordances, content items, and selectable tags described above withreference to method 800 optionally have one or more of thecharacteristics of the transport interfaces, tag modificationaffordances, transport option affordances, content items, and selectabletags described herein with reference to other methods described herein(e.g., the methods 900 and 1000). For brevity, these details are notrepeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A, 3, and 5A) orapplication specific chips. Further, the operations described above withreference to FIGS. 8A-8C, optionally, implemented by components depictedin FIGS. 1A-1B. For example, the selection inputs, the inputs forremoving the association between a tag and a content item, and theinputs for adding an association between a tag and a content item are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive surface 604, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 9A-9D illustrate a flow diagram of a method 900 of jointlyaccessible content items within a collaboration interface in accordancewith some embodiments. The method 900 is performed at an electronicdevice (e.g., the portable multifunction device 100 in FIG. 1A, or thedevice 300 in FIG. 3) with one or more processors, non-transitorymemory, a display, and one or more input devices. In some embodiments,the display is a touch-screen display and the one or more input devicesis on or integrated with the display (e.g., the device is a tablet orsmartphone). In some embodiments, the display is separate from the oneor more input devices (e.g., the device is a laptop with a separatedisplay and touchpad, or desktop computer with a separate display andmouse). Some operations in method 900 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 900 provides an intuitive way to viewjointly accessible content items. The method reduces the cognitiveburden on a user when viewing jointly accessible content items, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to view jointly accessible contentitems faster and more efficiently conserves power and increases the timebetween battery charges.

The device detects (902), via the one or more input devices, a firstinput that corresponds to selection of a collaboration affordance. Asone example, the collaboration affordance corresponds to one of aplurality of affordances displayed at the bottom of a documentmanagement application that also includes a projects affordance and abrowse affordance. As one example, in FIG. 6K, the device 100 detects acontact 673 selecting the collaboration view affordance 658 a.

In response to detecting the selection of the collaboration affordance,the device displays (904), on the display, a collaboration interface(e.g., a project management portal for managing project status for ateam of multiple collaborators), including concurrently displaying: arecent-items region that includes a plurality of representations of aplurality of recently modified content items (e.g., apresentation/slide-deck, note, email, image, message, word processingdocument, spreadsheet, audio file, video, electronic document, or thelike) that includes one or more content items that are not jointlyaccessible by other users; and a collaborative-items region thatincludes a plurality of representations of a plurality of jointlyaccessible content items that are jointly accessible by the other users.According to some embodiments, the collaboration interface provides aseamless user experience with increased visibility and contextualinformation that requires less time and user inputs when viewingrecently modified and/or accessed content items and jointly accessiblecontent items, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

For example, the other users correspond to one or more collaborators, ora specific group of collaborators. In some embodiments, the recent-itemsregion also includes representations of recently viewed content items.In some embodiments, the plurality of representations within therecent-items region correspond to thumbnail images or icons of theassociated content items. In some embodiments, the plurality ofrepresentations within the collaborative-items region correspond tothumbnail images or icons of the associated content items. In someembodiments, the plurality of representations within the recent-itemsregion includes text descriptions of the associated content items. Insome embodiments, the plurality of representations within thecollaborative-items region includes text descriptions of the associatedcontent items.

In some embodiments, metadata is displayed proximate to each of theplurality of representations within the recent-items region. Forexample, the metadata includes the name, size, location, modificationdate, creation date, creator's name, and/or the like for the associatedcontent items. According to some embodiments, the recent-items regionhas a different colored background than other regions within thecollaboration interface.

In some embodiments, metadata is displayed proximate to each of theplurality of representations within the collaborative-items region. Forexample, the metadata includes the name, size, location, modificationdate, creation date, creator's name, and/or the like for the associatedcontent items. According to some embodiments, the jointly accessiblecontent items correspond to a collaboration mode (e.g., live sharing notstatically emailed or texted to others) where others users have readand/or write access to the jointly accessible content items.

For example, in response to detecting the selection of the collaborationview affordance 658 a in FIG. 6K, the device 100 displays acollaboration interface 680 in FIG. 6L. As shown in FIG. 6L, thecollaboration interface 680 includes a recent-items region 682 with aplurality of representations of a plurality of recently modified contentitems and a collaborative-items region 692 with a plurality ofrepresentations of a plurality of jointly accessible content items thatare jointly accessible by other users. According to some embodiments,the recent-items region 682 includes representations of one or morecontent items that are not jointly accessible by the other users.

As shown in FIG. 6L, the recent-items region 682 includes content itemrepresentations 684 a, 684 b, 684 c, 684 d, 684 e, 684 f, 684 g, 684 h,684i, 684 j, 684k, 6841, 684m, and 684n (sometimes collectively referredto herein as the “representations 684”). In some embodiments, therepresentations 684 correspond to content items that were recentlymodified and/or viewed by the user of the device 100. In someembodiments, the representations 684 correspond to content items thatwere recently modified and/or viewed by members of a group of users(e.g., a collaboration or project group). According to some embodiments,at least some of the representation 684 correspond to content items thatare not jointly accessible by others user.

As shown in FIG. 6L, the collaborative-items region 692 includes contentitem representations 694 a, 694 b, 694 c, 694 d, 694 e, 694 f, and 694 g(sometimes collectively referred to herein as the “representations694”). In some embodiments, the representations 694 correspond tocontent items that are jointly accessible to other users. In someembodiments, the other users correspond to members of a group of users(e.g., a collaboration or project group). For example, the group ofusers is selected by a project leader or administrator. For example, theproject leader or administrator also sets privileges (e.g., read and/orwrite access) for each of the users in the group of users.

In some embodiments, metadata is displayed (906) proximate to each ofthe plurality of representations of the plurality of jointly accessiblecontent items indicating recent activity associated with a respectiveshared content item. In some embodiments, the metadata includesinformation corresponding to the type of activity (e.g., read or write),the time of activity, and/or the like. In some embodiments, the metadataincludes information corresponding to the user responsible for theactivity. In some embodiments, the metadata includes a badge thatindicates any activity (e.g., an “unread messages,” “new activity,” oractivity count indicator). According to some embodiments, the metadatais displayed within the collaboration interface to provide a seamlessuser experience with additional contextual information that requiresless time and user inputs when viewing recently modified and/or accessedcontent items and jointly accessible content items, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

For example, in FIG. 6L, the recent-items region 682 includesrepresentations 684 and associated metadata 686 a, 686 b, 686 c, 686 d,686 e, 686 f, 686 g, 686 h, 686 i, 686 j, 686 k, 686 l, 686 m, and 686n. For example, the metadata includes the name, size, location,modification date, creation date, creator's name, and/or the like forthe associated content items. For example, in FIG. 6L, thecollaborative-items region 692 includes content item representations 694and associated metadata 696 a, 696 b, 696 c, 696 d, 696 e, 696 f, and696 g. For example, the metadata includes the name, size, location,modification date, creation date, creator's name, and/or the like forthe associated content items.

In some embodiments, the recent-items region includes (908) a firstaffordance provided to display additional representations of theplurality of recently modified content items when selected, and thecollaborative-items region includes a second affordance provided todisplay additional representations of the plurality of jointlyaccessible content items. For example, in FIG. 6L, the recent-itemsregion 682 includes a “See more” affordance 688 provided to seeadditional representations of the plurality of recently modified contentitems in response to selection thereof (e.g., with a tap/selectiongesture). Similarly, as another example, in FIG. 6L, thecollaborative-items region 692 also includes a “See more” affordance 698provided to see additional representations of the plurality of jointlyaccessible content items in response to selection thereof (e.g., with atap/selection gesture).

In some embodiments, the plurality of recently modified content itemscorresponds to (910) recently modified content items aggregated from atleast one of: one or more storage location, or one or more differentapplication, and the plurality of jointly accessible content itemscorresponds to jointly accessible content items aggregated from at leastone of: two or more storage locations, or two or more different storageservices (e.g., cloud storage services). According to some embodiments,the aggregation of recently modified content items and jointlyaccessible content items across multiple storage locations, application,and/or storage services provides a seamless user experience withincreased visibility and contextual information that requires less timeand user inputs when viewing recently modified and/or accessed contentitems and jointly accessible content items, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the different storage locations correspond to oneor more local storage devices, one or more remote storage devices, oneor more attached/peripheral storage devices, one or morefolders/directories, and/or the like. In some embodiments, the differentstorage services are represented on the device by differentapplications.

In some embodiments, displaying the collaboration interface includes(912) concurrently displaying a tags region (sometimes also hereincalled a “projects region”) that includes a plurality of tags associatedwith the plurality of recently modified content items and the pluralityof jointly accessible content items. According to some embodiments, thetags region of the collaboration interface provides a seamless userexperience with increased visibility and contextual information thatrequires less time and user inputs when filtering content items based ontags, which, additionally, reduces power usage and improves battery lifeof the device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device 100 concurrently displays the tagsregion in addition to the recent-items region (or a portion thereof). Insome embodiments, the device 100 concurrently displays the tags regionin addition to the collaborative-items region (or a portion thereof).According to some embodiments, when the collaboration interface isinitially displayed, the tags region is not fully visible. For example,the tags region is accessed/viewed by scrolling down within thecollaboration interface.

As one example, in FIG. 6M, the device 100 detects a first scrollinggesture (e.g., a swipe or tap-and-drag gesture) with a contact 683 in afirst direction (e.g., vertical) within the collaboration interface 680.Continuing with this example, in response to detecting the firstscrolling gesture, the device 100 scrolls the collaboration interface680 in a downward direction. As a result, in FIG. 6N, the collaborationinterface 680 includes a projects region 6102 and a collaborators region6112 in addition to the collaborative-items region 692 and a portion ofthe recent-items region 682. As shown in FIG. 6N, the projects region6102 includes a plurality of selectable tags 6104 a, 6104 b 6104 c, 6104d, 6104 e, and 6104 f (sometimes collectively referred to herein as the“tags 6104”). For example, the tags 6104 correspond to tags that areassociated with the content items that correspond to the representations684 and 694. In another example, the tags 6104 correspond to frequentlyused tags, recently used tags, and/or the like.

In some embodiments, the device (914): detects, via the one or moreinput devices, a second input that corresponds to selection of arespective tag among the plurality of tags in the tags region (e.g., tapor click on the respective tag); and, in response to detecting theselection of the respective tag: updates the recent-items region toinclude a subset of the plurality of representations of the plurality ofrecently modified content items that is associated with the respectivetag (e.g., display representations within the recent-items region forthose recently modified content items that are tagged with therespective tag); and updates the collaborative-items region to include asubset of the plurality of representations of the plurality of jointlyaccessible content items that is associated with the respective tag(e.g., display representations within the recent-items region forrecently modified content items that are tagged with the respectivetag). According to some embodiments, the ability to filter therecent-items region and the collaborative items region of thecollaboration interface based on tags provides a seamless and morecustomized user experience that requires less time and user inputs whenviewing recently modified and/or accessed content items and/or jointlyaccessible content items, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, two or more tags are selected, and the recent-itemsregion and collaborative-items region are sorted accordingly. Forexample, those content items that match two tags are sorted higher thanthose content items that match one tag. In some embodiments, instead offiltering within the collaboration interface, the filtered results areshown within a file explorer interface that replaces the collaborationinterface. In some embodiments, instead of filtering within thecollaboration interface, the filtered results are shown within aprojects interface that replaces the collaboration interface.

According to some embodiments, in response to detecting an input thatcorresponds to selecting a respective tag, and in accordance with adetermination that the input satisfies a filtering criterion (e.g., aclick input, tap input, or the like), the device 100 filters theplurality of representations of the plurality of recently modifiedcontent items within the recent-items region based on the respective tagand also filters the plurality of representations of the plurality ofjointly accessible content items within the collaborative-items regionbased on the respective tag. As one example, FIGS. 6O-6P show a sequencein which the device 100 filters the content item representationsdisplayed within the collaborative-items region 692 of the collaborationinterface 680 based on the selected tag 6104 f (e.g., the “Finance” tag)in response to detecting the selection of the tag 6104 f that satisfiesthe filtering criterion.

In some embodiments, the device (916): detects, via the one or moreinput devices, a second input that corresponds to selection of arespective tag among the plurality of tags in the tags region (e.g., tapor click on the respective tag); and, in response to detecting theselection of the respective tag, replaces display of the collaborationinterface with a projects interface that includes a first regionassociated with the respective tag with a plurality of representationsof content items associated with the respective tag. According to someembodiments, the projects interface provides a seamless user experiencethat requires less time and user inputs when viewing content items basedon tag/project, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

For example, the projects interface includes one row for eachproject/tag. In this example, the user is able to scroll within the rowsto see more representations associated with a project/tag. In someembodiments, the plurality of representations of content itemsassociated with the respective tag includes thumbnail images or iconsassociated with the content items. In some embodiments, the plurality ofrepresentations of content items associated with the respective tagincludes text descriptions of the content items.

According to some embodiments, in response to detecting an input thatcorresponds to selecting a respective tag, and in accordance with adetermination that the input satisfies a view replacement criterion(e.g., a hover input, double click input, double tap input, long pressinput, deep press input, or the like), the device 100 replaces displayof the collaboration interface with the projects interface with a regionassociated with the selected tag that includes representations ofcontent items associated with the selected tag in response to detectingthe selection of the tag that satisfies the view replacement criterion.

As one example, in FIG. 6T, the device 100 displays the projectsinterface 6130 with a first project region 6142 a associated with the“Brainstorming” tag 6104 a, a second project region 6142 b associatedwith the “Motorcycles” tag 6104 b, and a third project region 6142 cassociated with the “Leather Jackets” tag 6104 c. In FIG. 6T, the firstproject region 6142 a includes content item representations 6132 a, 6132b, 6132 c, 6132 d, 6132 e, and 6132 f and associated metadata 6134 a,6134 a, 6134 c, 6134 d, 6134 e, and 6134 f that correspond to contentitems associated with the “Brainstorming” tag 6104 a. For example, themetadata includes the name, size, location, modification date, creationdate, creator's name, and/or the like for the associated content items.

In some embodiments, the projects interface also includes (918) a secondregion associated with a different tag with a plurality ofrepresentations of content items associated with the different tag. Forexample, the metadata includes the name, size, location, modificationdate, creation date, creator's name, and/or the like for the associatedcontent items. According to some embodiments, the projects interfaceprovides a seamless user experience with increased visibility andcontextual information that requires less time and user inputs whenviewing content items based on tag/project, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. For example, in FIG. 6T,the second project region 6142 b of the projects interface 6130 includescontent item representations 672 a, 672 b, 672 c, 672 d, and 672 e(sometimes collectively referred to herein as the “representations 672”)and associated metadata 676 a, 676 b, 676 c, 676 d, and 676 e thatcorrespond to content items associated with the “Motorcycles” tag 6104 b(e.g., similar to FIG. 6J).

In some embodiments, displaying the collaboration interface includes(920) concurrently displaying a collaborators region that includes aplurality of representations of a plurality of collaborators associatedwith the plurality of recently modified content items and the pluralityof jointly accessible content items. According to some embodiments, thecollaborators region of the collaboration interface provides a seamlessuser experience with increased visibility and contextual informationthat requires less time and user inputs when filtering content itemsbased on collaborators, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the device 100 concurrently displays thecollaborators region in addition to the recent-items region (or aportion thereof). In some embodiments, the device 100 concurrentlydisplays the collaborators region in addition to the collaborative-itemsregion (or a portion thereof). According to some embodiments, when thecollaboration interface is initially displayed, the collaborators regionis not fully visible. For example, the collaborators region isaccessed/viewed by scrolling down within the collaboration interface.

In some embodiments, the plurality of representations of the pluralityof collaborators includes thumbnail images or avatars associated withthe collaborators. In some embodiments, the plurality of representationsof the plurality of collaborators includes a name, handle, quote, blurb,or other text associated with the collaborators. In some embodiments,metadata is displayed proximate to the plurality of representations ofthe plurality of collaborators includes. For example, the metadataincludes the collaborator name, collaborator location, collaboratorteam/group, collaborator projects, collaborator availability,collaborator blurb, total number of collaborator modifications,time/date of last modification by collaborator, etc.

As one example, in FIG. 6M, the device 100 detects a first scrollinggesture (e.g., a swipe or tap-and-drag gesture) with a contact 683 in afirst direction (e.g., vertical) within the collaboration interface 680.Continuing with this example, in response to detecting the firstscrolling gesture, the device 100 scrolls the collaboration interface680 in a downward direction. As a result, in FIG. 6N, the collaborationinterface 680 includes a projects region 6102 and a collaborators region6112 in addition to the collaborative-items region 692 and a portion ofthe recent-items region 682. As shown in FIG. 6N, the collaboratorsregion 6112 includes a selectable collaborator representations 6114 a,6114 b 6114 c, 6114 d, 6114 e, 6114 f, and 6114 h (sometimescollectively referred to herein as the “collaborator representations6114”).

In some embodiments, each of the collaborator representations 6114corresponds to person with access to the content items that correspondto the representations 694 within the collaborative-items region 692.For example, a project supervisor authorizes and/or invites users towork and collaborate on a project. In this example, theauthorized/invited users are given to read and/or write access to thejointly accessible content items that correspond to the representations694 within the collaborative-items region 692. In some embodiments, eachof the collaborator representations 6114 includes an image, avatar, orportrait of a corresponding collaborator. In some embodiments, metadatais displayed proximate to each of the collaborator representations 6114.For example, the metadata includes the associated collaborator's name,title, access details, phone number, email address, residential address,office location, availability, and/or the like.

In some embodiments, the device (922): detects, via the one or moreinput devices, a third input that corresponds to selection of arespective representation corresponding to a respective collaboratoramong the plurality of representations of the plurality of collaborators(e.g., tap or click on the respective collaborator); and, in response todetecting the selection of the respective representation correspondingto the respective collaborator: updates the recent-items region toinclude a subset of the plurality of representations of the plurality ofrecently modified content items that is associated with the respectivecollaborator (e.g., display representations for those content items thathave recently been modified by the respective collaborator); and updatesthe collaborative-items region to include a subset of the plurality ofrepresentations of the plurality of jointly accessible content itemsthat is associated with the respective collaborator (e.g., displayrepresentations for those content items that were shared by therespective collaborator). In some embodiments, instead of filteringwithin the collaboration interface, the filtered results are shownwithin a file explorer interface that replaces the collaborationinterface. According to some embodiments, the ability to filter therecent-items region and the collaborative items region of thecollaboration interface based on collaborator provides a seamless andmore customized user experience that requires less time and user inputswhen viewing recently modified and/or accessed content items and/orjointly accessible content items, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

According to some embodiments, in response to detecting an input thatcorresponds to selecting a respective representation corresponding to arespective collaborator, and in accordance with a determination that theinput satisfies a filtering criterion (e.g., a click input, tap input,or the like), the device 100 filters the plurality of representations ofthe plurality of recently modified content items within the recent-itemsregion based on the respective collaborator and also filters theplurality of representations of the plurality of jointly accessiblecontent items within the collaborative-items region based on therespective collaborator. As one example, FIGS. 6P-6Q show a sequence inwhich the device 100 filters the content item representations displayedwithin the collaborative-items region 692 of the collaboration interface680 based on the collaborator that corresponds to the selectedcollaborator representation 6114 h in response to detecting theselection of the collaborator representation 6114 h that satisfies thefiltering criterion.

In some embodiments, the device (924): detects, via the one or moreinput devices, a third input that corresponds to selection of arespective representation corresponding to a respective collaboratoramong the plurality of representations of the plurality of collaborators(e.g., tap or click on the respective collaborator); and, in response todetecting the selection of the respective representation correspondingto the respective collaborator, displays, on the display, a userinformation interface (e.g., a contact card) that includes informationassociated with the respective collaborator. According to someembodiments, the user information interface provides a seamless userexperience that requires less time and user inputs when viewing userinformation for a collaborator, which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the information associated with the respectivecollaborator corresponds to collaborator metadata. For example, thecollaborator metadata includes the collaborator name, collaboratorlocation, collaborator team/group, collaborator projects, collaboratoravailability, collaborator blurb, total number of collaboratormodifications, time/date of last modification by collaborator, etc.

According to some embodiments, in response to detecting an input thatcorresponds to selecting a respective representation corresponding to arespective collaborator, and in accordance with a determination that theinput satisfies a user information preview criterion (e.g., a hoverinput, double click input, double tap input, long press input, deeppress input, or the like), the device 100 displays a user informationinterface (e.g., a contact card) associated with the respectivecollaborator. As one example, FIGS. 6Q-6R show a sequence in which thedevice 100 displays user information interface 6115 for the collaboratorthat corresponds to the selected collaborator representation 6114 c inresponse to detecting the selection of the collaborator representation6114 c that satisfies the user information preview criterion.

In some embodiments, displaying the collaboration interface includes(926) concurrently displaying a locations region that includes aplurality of representations of a plurality of locations associated witha plurality of content items (e.g., recently modified and jointlyaccessible content items, or all content items accessible to the user ofthe device). According to some embodiments, the locations region of thecollaboration interface provides a seamless user experience withincreased visibility and contextual information that requires less timeand user inputs, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

For example, the plurality of locations corresponds to local storagedevices, remote storage devices, attached/peripheral storage devices,folders/directories, and/or the like. In some embodiments, the device100 concurrently displays the locations region in addition to therecent-items region (or a portion thereof). In some embodiments, thedevice 100 concurrently displays the locations region in addition to thecollaborative-items region (or a portion thereof). In some embodiments,the device 100 concurrently displays the locations region in addition tothe recent-items region (or a portion thereof) and thecollaborative-items region (or a portion thereof). In some embodiments,the locations region includes a plurality of representations of aplurality of locations associated with a plurality of content items.According to some embodiments, when the collaboration interface isinitially displayed, the locations region is not fully visible. Forexample, the locations region is accessed/viewed by scrolling downwithin the collaboration interface.

In some embodiments, each of the plurality of representations of theplurality of locations indicates the location via text, an icon, animage, and/or the like. In some embodiments, selection of one of theplurality of representations of the plurality of locations associatedcauses the collaborative-items and recent-items regions to be filteredwithin the collaboration interface based on the corresponding storagelocation. In some embodiments, selection of one of the plurality ofrepresentations of the plurality of locations causes thecollaborative-items and recent-items regions to be filtered based on thecorresponding storage location within a file explorer interface thatreplaces the collaboration interface.

As one example, in FIG. 6R, the device 100 detects a third scrollinggesture (e.g., a swipe or tap-and-drag gesture) with a contact 695 inthe first direction (e.g., vertical) within the collaboration interface680. Continuing with this example, in response to detecting the thirdscrolling gesture, the device 100 scrolls the collaboration interface680 in a downward direction. As a result, in FIG. 6S, the collaborationinterface 680 includes a locations region 6122 in addition to a portionof the collaborative-items region 692, the projects region 6102, and thecollaborators region 6112.

In FIG. 6S, the locations region 6122 includes storage locationrepresentations 6124 a, 6124 b, 6124 c, and 6124 d (sometimescollectively referred to herein as the “location representations 6124”)and associated metadata 6126 a, 6126 b, 6126 c, and 6126 d for differentstorage locations (e.g., cloud storage services, local storage devices,remote storage devices, and/or attached/peripheral storage devices suchas USB devices). For example, the associated metadata includes anindication of access privileges, total capacity, free space, uptime,storage device name, storage device type, and/or the like.

In some embodiments, the device (928): detects, via the one or moreinput devices, a fourth input that corresponds to navigating within thecollaboration interface (e.g., swipe or tap-and-drag gesture); and, inresponse to detecting the fourth input: in accordance with adetermination that the fourth input corresponds to a first input type(e.g., horizontal swipe gesture), scrolls a portion of at least one ofthe recent-items region or the collaborative-items region substantiallyhorizontally; and, in accordance with a determination that the fourthinput corresponds to a second input type (e.g., vertical swipe gesture),scrolls a portion of the collaboration interface substantiallyvertically. According to some embodiments, the ability to scroll withina region of the collaboration interface or to scroll the collaborationinterface itself provides a seamless user experience that requires lesstime and user inputs when viewing recently modified and/or accessedcontent items and jointly accessible content items, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

As one example, FIGS. 6M-6N show a sequence in which the device 100scrolls the collaboration interface 680 in a downward direction inresponse to detecting a first scrolling gesture (e.g., a swipe ortap-and-drag gesture) with a contact 683 in a first direction (e.g.,vertical) within the collaboration interface 680. As another example,FIGS. 6N-6O show a sequence in which the device 100 scrolls thecollaborative-items region 692 of the collaboration interface 680 in aright-to-left direction in response to detecting a second scrollinggesture (e.g., a swipe or tap-and-drag gesture) with a contact 687 in asecond direction (e.g., horizontal) within the collaborative-itemsregion 692.

In some embodiments, the device (930): detects, via the one or moreinput devices, a fifth input that corresponds to selection of arespective representation from among the plurality of representations inthe recent-items region or the plurality of representations in thecollaborative-items region; and, in response to detecting the selectionof the respective representation and in accordance with a determinationthat the fifth input satisfies a content preview criterion, displays, onthe display a preview of a content item associated with the respectiverepresentation. In some embodiments, the preview of the content item isoverlaid on the collaboration interface. According to some embodiments,the content preview interface provides a seamless user experience thatrequires less time and user inputs when viewing a preview for a contentitem, which, additionally, reduces power usage and improves battery lifeof the device by enabling the user to use the device more quickly andefficiently.

According to some embodiments, in response to detecting an input thatcorresponds to selecting a respective content item representation, andin accordance with a determination that the input satisfies a contentpreview criterion (e.g., a click input, tap input, or the like), thedevice 100 displays a content preview interface for the content itemthat corresponds to the selected respective content item representation.As one example, FIGS. 6L-6M show a sequence in which the device 100displays a content preview interface 685 in response to detecting theselection of the content item representation 684 j that satisfies thecontent preview criterion.

In some embodiments, in response to detecting the selection of therespective representation and in accordance with a determination thatthe fifth input satisfies an application launch criterion, the device(932): launches an application that corresponds to the content itemassociated with the respective representation; and replaces display ofthe collaboration interface with an interface associated with theapplication that includes the content item associated with therespective representation. According to some embodiments, the ability tolaunch an application through the collaboration interface provides aseamless user experience that requires less time and user inputs, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

According to some embodiments, in response to detecting an input thatcorresponds to selecting a respective content item representation, andin accordance with a determination that the input satisfies anapplication launch criterion (e.g., a hover input, double click input,double tap input, long press input, deep press input, or the like), thedevice 100 launches an application associated with the content item thatcorresponds to the selected respective content item representation andreplaces display of the collaboration interface with an applicationinterface for the application associated with the content item thatcorresponds to the selected respective content item representation inresponse to detecting the selection of the content item representationthat satisfies the application launch criterion. For example, theapplication interface includes the content item that corresponds to theselected respective content item representation.

It should be understood that the particular order in which theoperations in FIGS. 9A-9D have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,the methods 800 and 1000) are also applicable in an analogous manner tomethod 900 described above with respect to FIGS. 9A-9D. For example, thecollaboration interfaces, representations of recently modified contentitems, representations of jointly accessible content items, selectabletags, representations of collaborators, and representations of locationdescribed above with reference to method 900 optionally have one or moreof the characteristics of the collaboration interfaces, representationsof recently modified content items, representations of jointlyaccessible content items, selectable tags, representations ofcollaborators, and representations of location described herein withreference to other methods described herein (e.g., the methods 800 and1000). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A, 3, and 5A) orapplication specific chips. Further, the operations described above withreference to FIGS. 9A-9D, optionally, implemented by components depictedin FIGS. 1A-1B. For example, the selection inputs, scrolling inputs, andfiltering inputs are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive surface 604, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

FIGS. 10A-10C illustrate a flow diagram of a method 1000 of previewingcontent items and tags associated with an application in accordance withsome embodiments. The method 1000 is performed at an electronic device(e.g., the portable multifunction device 100 in FIG. 1A, or the device300 in FIG. 3) with a display, a touch-sensitive surface, and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. In some embodiments, the display is a touch-screen display andthe one or more input devices is on or integrated with the display(e.g., the device is a tablet or smartphone). In some embodiments, thedisplay is separate from the one or more input devices (e.g., the deviceis a laptop with a separate display and touchpad, or desktop computerwith a separate display and mouse). Some operations in method 1000 are,optionally, combined and/or the order of some operations is, optionally,changed.

As described below, the method 1000 provides an intuitive way to previewcontent items and tags associated with an application. The methodreduces the cognitive burden on a user when previewing content items andtags associated with an application, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to preview content items and tags associated with anapplication faster and more efficiently conserves power and increasesthe time between battery charges.

The device displays (1002), on the display, a user interface thatincludes one or more application icons. In some embodiments, the devicedisplays the one or more application icons on the home screen (e.g., asmart phone or tablet home screen with a plurality of application launchicons and/or widgets or a computer desktop). In some embodiments, thedevice displays the one or more application icons within a dock on thehome screen. In some embodiments, the device displays the one or moreapplication icons within a quick access dock overlaid on an applicationinterface or application window. As one example, in FIG. 7A, the device100 displays the application icons 702 within the home screen interface700 outside of the dock region 704. As another example, in FIG. 7A, thedevice 100 displays the application icons 706 within the dock region704. As yet another example, in FIG. 7K, the device 100 displays theapplication icons 706 within the quick access dock region 745.

While displaying the user interface, the device detects (1004), via theone or more input devices, a first input that corresponds to selectionof a respective application icon among the one or more applicationicons.

In response to detecting the selection of the respective applicationicon, and in accordance with a determination that the first inputsatisfies a content preview criterion (e.g., a hover input, double clickinput, double tap input, long press input, deep press input, or thelike), the device (1006) displays, on the display, a preview interface(e.g., a pop-over panel, pane, window, or the like) without launchingthe application, where the preview interface includes: a plurality ofrepresentations of a plurality of content items (e.g.,presentation/slide-deck, note, email, image, message, word processingdocument, spreadsheet, audio file, video, electronic document, and/orthe like) corresponding to the application associated with therespective application icon; and a plurality of representations of aplurality of tags corresponding to the application associated with therespective application icon. According to some embodiments, therepresentations of content items and/or tags within the previewinterface provide a seamless user experience with additional contextualinformation that requires less time and user inputs when performingtasks and launching applications, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

In some embodiments, the plurality of representations of the pluralityof content items includes thumbnail images or icons associated with thecontent items. In some embodiments, the plurality of representations ofthe plurality of content items includes text descriptions of the contentitems. In some embodiments, the plurality of representations of theplurality of content items includes metadata associated with the contentitems. For example, the metadata includes the name, size, location,modification date, creation date, creator's name, and/or the like of thecontent items.

In some embodiments, the plurality of representations of the pluralityof tags corresponds to the tags associated with the content items thatcorrespond to the plurality of representations of the plurality ofcontent items. In some embodiments, the plurality of representations ofthe plurality of tags corresponds to the recently and/or frequently usedtags.

According to some embodiments, in response to detecting an input thatcorresponds to selecting a respective application icon, and inaccordance with a determination that the input satisfies a contentpreview criterion (e.g., a hover input, double click input, double tapinput, long press input, deep press input, or the like), the device 100displays a preview interface associated with the respective selectedapplication icon. As one example, FIGS. 7A-7B show a sequence in whichthe device 100 displays the preview interface 710 for the file browserapplication that corresponds to the application icon 706 a in responseto detecting the selection of the application icon 706 a that satisfiesthe content preview criterion.

As shown in FIG. 7B, the preview interface 710 for the file browserapplication includes a plurality of content item representations 714 a,714 b, 714 c, 714 d, 714 e, and 714 f (sometimes collectively referredto herein as the “representations 714”) for content items (e.g.,presentations/slide-decks, notes, emails, images, messages, wordprocessing documents, spreadsheets, audio files, videos, electronicdocuments, and/or the like). In another example, the representations 714correspond to frequently viewed and/or modified content items, recentlyviewed and/or modified content items, and/or the like. As shown in FIG.7B, the preview interface 710 for the file browser application alsoincludes a plurality of tag representations 708 a, 708 b, and 708 c(sometimes collectively referred to herein as the “representations 708”)for tags. For example, the representations 708 correspond to tags thatare associated with the content items that correspond to therepresentations 714. In another example, the representations 708correspond to frequently used tags, recently used tags, and/or the like.

In response to detecting the selection of the respective applicationicon, and in accordance with a determination that the first inputsatisfies an application launch criterion (e.g., a click input, tapinput, or the like), the device launches (1010) an applicationassociated with the respective application icon. According to someembodiments, in response to detecting an input that corresponds toselecting a respective application icon, and in accordance with adetermination that the input satisfies an application launch criterion(e.g., a click input, tap input, or the like), the device 100 launchesthe application associated with the respective selected application iconand displays an application interface for the application associatedwith the respective selected application icon. As one example, FIGS.7I-7J show a sequence in which the device 100 launches a presentationcreation application and displays a presentation creation interface 730associated with the presentation creation application in response todetecting the selection of the application icon 706 e that satisfies theapplication launch criterion.

In some embodiments, the application launch criterion is satisfied(1008) when the first input corresponds to one of: a tap input, or aclick input, and the content preview criterion is satisfied when thefirst input corresponds to one of: a long press input that has aduration that is greater than a press duration threshold, a hover inputthat has a duration that is greater than a hover duration threshold, adeep press input that has an intensity that is greater than an intensitythreshold, a double tap input, or a double click input.

In some embodiments, the plurality of content items is selected (1012)based on at least one of: frequency of use, recency of use, orcontextual information associated with the respective application icon.According to some embodiments, the representations of content itemswithin the preview interface provides a seamless user experience withadditional contextual information that requires less time and userinputs when performing tasks and launching applications, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device selects the plurality of content itemsbased on frequently viewed/modified content items associated with theapplication that corresponds to the selected application icon. In someembodiments, the device selects the plurality of content items based onrecently viewed/modified content items associated with the applicationthat corresponds to the selected application icon. In some embodiments,the device sorts the plurality of content items based on content itemsize, content item name, creator name, last modifier name, frequency ofwrite modifications, frequency of read actions, recency of writemodification, recency of read action, and/or the like.

In some embodiments, the plurality of content items is stored across twoor more local storage devices, two or more remote storage devices, twoor more attached/peripheral storage devices, two or more storageservices, and/or the like. In some embodiments, the plurality of contentitems is stored across two or more storage services (e.g., cloud storageservices). In some embodiments, the device displays metadata proximateto each of the plurality of representations of a plurality of contentitems. For example, the metadata corresponds to the content item name,the content item location, the content item extension, the creationtime/date of the content item, the last modification time/date of thecontent item, the user who created the content item, the user who lastmodified the content item, the content item size, and/or the like.

In some embodiments, the plurality of tags is selected (1014) based onat least one of: frequency of use, recency of use, or contextualinformation associated with the respective application icon. Accordingto some embodiments, the representations of tags within the previewinterface provides a seamless user experience with additional contextualinformation that requires less time and user inputs when performingtasks and launching applications, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

In some embodiments, the device selects the plurality of tags to includetags associated with frequently viewed/modified content items. In someembodiments, the device selects the plurality of tags to include tagsassociated with recently viewed/modified content items associated withthe application that corresponds to the selected application icon. Insome embodiments, the device selects the plurality of tags to includefrequently used tags across a plurality of applications or a pluralityof storage services (e.g., different cloud storage services). In someembodiments, the device selects the plurality of tags to includerecently used tags across all applications or storage services (e.g.,cloud storage services). In some embodiments, the plurality of tags issorted based on global usage across all applications or storage services(e.g., cloud storage services). In some embodiments, the plurality oftags is sorted based on global usage across the application or storageservice corresponding to the selected application icon. In someembodiments, the plurality of tags is sorted based on local usage of theapplication or storage service corresponding to the selected applicationicon.

In some embodiments, the plurality of tags is associated with contentitems that are stored across two or more local storage devices, two ormore remote storage devices, two or more attached/peripheral storagedevices, two or more storage services, and/or the like. In someembodiments, the plurality of tags is associated with content items thatare stored across two or more storage services (e.g., cloud storageservices). In some embodiments, the plurality of tags is associated withcontent items that correspond to two or more applications.

In some embodiments, the device (1016): detects, via the one or moreinput devices, a second input that corresponds to selection of a firstrepresentation of a first tag among the plurality of representations ofthe plurality of tags in the preview interface; and, in response todetecting the selection of the first representation associated with thefirst tag, updates the plurality of representations of the plurality ofcontent items to include content items that are associated with thefirst tag. According to some embodiments, the ability to filter therepresentations of content items within the preview interface based on atag provides a seamless user experience with additional contextualinformation that requires less time and user inputs when performingtasks and launching applications, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

For example, the filtered content items are sorted based on at least oneof: content item size, content item name, creator name, last modifiername, frequency of write modifications, frequency of read actions,recency of write modification, recency of read action, and/or the like.In some embodiments, in response to detecting the selection of the firstrepresentation associated with the first tag, the device also displaysan indication that the first tag has been selected such as a badge witha check mark, darkened border, thickened border, changed color, changedappearance state, blinking appearance, and/or the like.

As one example, FIGS. 7N-7O show a sequence in which the device 100filters the content item representations displayed within the previewinterface 710 in response to a first filtering operation that selectedthe tag representation 708 b associated with the “Learning” tag. Asshown in FIG. 7O, the representations 714 displayed within the previewinterface 710 are filtered to include the content item representations714 a, 714 b, 714 c, and 714 d for the content items that are associatedwith the “Learning” tag.

In some embodiments, the device (1018): detects, via the one or moreinput devices, a third input that corresponds to selection of a secondrepresentation of a second tag among the plurality of representations ofthe plurality of tags in the preview interface; and, in response todetecting the selection of the second representation of the second tag,updates the plurality of representations of the plurality of contentitems to include content items that are associated with at least one of:the first tag, or the second tag. According to some embodiments, theability to filter the representations of content items within thepreview interface based on two or more tags provides a seamless userexperience with additional contextual information that requires lesstime and user inputs when performing tasks and viewing content items,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, content items that match both the first tag AND thesecond tag are sorted ahead of content items that match the first tagXOR the second tag (e.g., content items that match the first tag ormatch the second tag, but do not match both the first tag and the secondtag). In some embodiments, in response to detecting the selection of thesecond representation associated of the second tag, the device alsodisplays an indication that the second tag has been selected such as abadge with a check mark, darkened border, thickened border, changedcolor, changed appearance state, blinking appearance, and/or the like.

As one example, FIGS. 7O-7P show a sequence in which the device 100further filters the content item representations displayed within thepreview interface 710 in response to a second filtering operation thatselected the tag representation 708 c associated with the “Study” tag.As shown in FIG. 7P, the representations 714 displayed within thepreview interface 710 are further filtered to include the content itemrepresentations 714 a and 714 b for the content items that areassociated with the “Learning” tag and the “Study” tag.

According to some embodiments, with reference to examples above in steps1016 and 1018, the preview interface 710 is updated to show content itemrepresentations for content items that match both the “Learning” tag andthe “Study” tag. According to some embodiments, with reference toexamples above in steps 1016 and 1018, the preview interface 710 isupdated to show content item representations for content items thatmatch the “Learning” tag or the “Study” tag. According to someembodiments, with reference to examples above in steps 1016 and 1018,the preview interface 710 is updated to show content itemrepresentations for content items that match the “Learning” tag and/orthe “Study” tag.

In some embodiments, the device (1020): detects, via the one or moreinput devices, a scrolling input within the preview interface; and, inresponse to detecting the scrolling input: in accordance with adetermination that the scrolling input is detected within a first regionof the preview interface that corresponds to the plurality ofrepresentations of the plurality of content items and the scrollinginput satisfies a first direction criterion (e.g., a substantiallyvertical swipe or tap-and-drag gesture), updates the plurality ofrepresentations of the plurality of content items to show differentrepresentations of the plurality of content items within the previewinterface; and, in accordance with a determination that the scrollinginput is detected within a second region of the preview interface thatcorresponds to the plurality of representations of the plurality of tagsand the scrolling input satisfies a second direction criterion (e.g., asubstantially horizontal swipe or tap-and-drag gesture), updates theplurality of representations of the plurality of tags to show differenttags of the plurality of tags within the preview interface. According tosome embodiments, the ability to scroll a first region of the previewinterface that includes the tag representations and also to scroll asecond region of the preview interface that includes the content itemrepresentations provides a seamless user experience with additionalcontextual information that requires less time and user inputs whenperforming tasks and viewing content items, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

According to some embodiments, in response to detecting a scrollinginput within the preview interface, and in accordance with adetermination that the scrolling input satisfies a first criterion(e.g., a substantially vertical swipe or tap-and-drag gesture within thesecond region associated with the plurality of representations of theplurality of content items), the device scrolls the second regionassociated with the plurality of representations of the plurality ofcontent items. As one example, FIGS. 7G-7H show a sequence in which thedevice 100 scrolls the second region 758 b that includes the pluralityof representations of the plurality of content items in a downwarddirection in response to detecting the first scrolling gesture (e.g., aswipe or tap-and-drag gesture) with a contact 731 in a first direction(e.g., vertical) within the second region 758 b of the preview interface750 that includes the representations 756.

According to some embodiments, in response to detecting a scrollinginput within the preview interface, and in accordance with adetermination that the scrolling input satisfies a second criterion(e.g., a substantially horizontal swipe or tap-and-drag gesture withinthe first region associated with the plurality of representations of theplurality of tags), the device scrolls the first region associated withthe plurality of representations of the plurality of tags. As oneexample, FIGS. 7H-7I show a sequence in which the device 100 scrolls thefirst region 758 a that includes the plurality of representations of theplurality of tags in a right-to-left direction in response to detectingthe second scrolling gesture (e.g., a swipe or tap-and-drag gesture)with a contact 733 in a second direction (e.g., horizontal) within thefirst region 758 a of the preview interface 750 that includes therepresentations 754.

In some embodiments, the user interface corresponds to (1022) a homescreen (e.g., a smart phone or tablet home screen with a plurality ofapplication launch icons and/or widgets or a computer desktop) thatincludes a dock region, and the one or more application icons aredisplayed within the dock region. According to some embodiments, theability to invoke the preview interface when interacting with anapplication icon in the dock region provides a seamless user experiencewith additional contextual information that requires less time and userinputs when performing tasks and launching applications, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently. As one example, FIGS. 7A-7B show a sequence in which thedevice 100 displays the preview interface 710 for the file browserapplication that corresponds to the application icon 706 a in responseto detecting the selection of the application icon 706 a within the dockregion 704 that satisfies the content preview criterion.

In some embodiments, the user interface corresponds to (1024) a homescreen (e.g., a smart phone or tablet home screen with a plurality ofapplication launch icons and/or widgets or a computer desktop) thatincludes the one or more application icons. According to someembodiments, the ability to invoke the preview interface wheninteracting with an application icon on the home screen and outside ofthe dock region provides a seamless user experience with additionalcontextual information that requires less time and user inputs whenperforming tasks and launching applications, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently. As one example,FIGS. 7F-7G show a sequence in which the device 100 displays the previewinterface 750 for the application (e.g., the application ABC) thatcorresponds to the application icon 702 f in response to detecting theselection of the application icon 702 f within the home screensinterface outside of the dock region 704 that satisfies the contentpreview criterion.

In some embodiments, the device (1026): detects, via the one or moreinput devices, a drag-and-drop input that corresponds to dragging arespective representation associated with a respective content itemamong the plurality of representations of the plurality of content itemsout of the preview interface and dropping the respective representationover a second application icon; and, in response to detecting completionof the drag-and-drop input (e.g., dropping the respective representationonto the second application icon): ceases to display the previewinterface; launches a second application associated with the secondapplication icon; and displays, on the display, the respective contentitem (e.g., an image or the like) within a second user interface thatcorresponds to the second application (e.g., creating a new email withan image or document). According to some embodiments, the ability todrag a content item representation out of the preview interface and dropthe content item representation over an application icon to launch anassociated application provides a seamless user experience withadditional contextual information that requires less time and userinputs when performing tasks and launching applications, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

As one example, FIGS. 7B-7D show a sequence in which the device 100launches a presentation creation application and displays thepresentation creation interface 730 associated with the presentationcreation application in response to detecting a drag-and-dropinput/gesture where the content item representation 714 f is dragged outof the preview interface 710 and dropped over the application icon 702 hassociated with the presentation creation application. As shown in FIG.7D, the content entry region 736 of the presentation creation interface730 includes a content item 715 (e.g., an image) that corresponds to thecontent item representation 714 f that was dragged-and-dropped over theapplication icon 702 h in FIGS. 7B-7C.

In some embodiments, the user interface corresponds to (1028) anapplication (e.g., an email, word processing, PDF creation, spreadsheet,presentation creation, etc. application), and the one or moreapplication icons are displayed within a quick-access dock regionoverlaid on the user interface that corresponds to the application.According to some embodiments, the ability to invoke the previewinterface when interacting with an application icon in the quick accessdock region provides a seamless user experience with additionalcontextual information that requires less time and user inputs whenperforming tasks and launching applications, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

For example, the user interface corresponds to an application interfaceor an application window in full-screen mode. In another example, theuser interface corresponds to an application interface or an applicationwindow in a tiled-mode. In yet another example, the user interfacecorresponds to an application interface or an application window in asplit-screen-mode. In some embodiments, the device displays thequick-access dock over the user interface in response to a detecting apredefined command (e.g., a predefined key combination such as ALT+TAB,a predefined gesture, a predefine key, selection of a predefinedaffordance, and/or the like). In some embodiments, the application iconsdisplayed within the quick-access dock are user-customizable.

As one example, FIGS. 7J-7K show a sequence in which the device 100displays the quick-access dock region 745 over the presentation creationinterface 730 in response to detecting a predefined gesture (e.g., aswipe or tap-and-drag gesture) with a contact 741 from a bottom edge ofthe display area in an upward direction. For example, the quick-accessdock region 745 slides up from the bottom edge of the display area inresponse to detecting the predefined gesture.

In some embodiments, the device (1032): detects, via the one or moreinput devices, a drag-and-drop input that corresponds to dragging arespective representation associated with a respective content itemamong the plurality of representations of the plurality of content itemsout of the preview interface and dropping the respective representationinto the user interface that corresponds to the application; and, inresponse to detecting completion of the drag-and-drop input (e.g.,dropping the respective representation into the user interface thatcorresponds to the application), displays, on the display, therespective content item (e.g., an image or the like) within the userinterface that corresponds to the application. According to someembodiments, the ability to drag a content item representation out ofthe preview interface and drop the content item representation over anapplication interface to export the associated content item into theapplication interface provides a seamless user experience withadditional contextual information that requires less time and userinputs when performing tasks, which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, in response to detecting completion of thedrag-and-drop input/gesture, the device ceases to display the respectiverepresentation in the preview interface. In some embodiments, inresponse to detecting completion of the drag-and-drop gestureinput/gesture, the device maintains display of the respectiverepresentation in the preview interface.

As one example, FIGS. 7M-7N show a sequence in which the device 100displays the content item 775 (e.g., an image) that corresponds to thecontent item representation 714 a within the content entry region 736 ofthe presentation creation interface 730 in response to detecting adrag-and-drop input/gesture where the content item representation 714 ais dragged out of the preview interface 710 and dropped over the contententry region 736 of the presentation creation interface 730. As shown inFIG. 7N, the content entry region 736 of the presentation creationinterface 730 includes a content item 775 (e.g., an image) thatcorresponds to the content item representation 714 a that wasdragged-and-dropped over the content entry region 736 of thepresentation creation interface 730 in FIGS. 7M.

It should be understood that the particular order in which theoperations in FIGS. 10A-10C have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,the methods 800 and 900) are also applicable in an analogous manner tomethod 1000 described above with respect to FIGS. 10A-10C. For example,the application icons, preview interfaces, representations of contentitems, and representations of tags described above with reference tomethod 1000 optionally have one or more of the characteristics of theapplication icons, preview interfaces, representations of content items,and representations of tags described herein with reference to othermethods described herein (e.g., the methods 800 and 900). For brevity,these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A, 3, and 5A) orapplication specific chips. Further, the operations described above withreference to FIGS. 10A-10C, optionally, implemented by componentsdepicted in FIGS. 1A-1B. For example, the application icon selectioninputs for displaying an associated preview interface, the applicationicon selection inputs for launching an associated application, thefiltering inputs, and the scrolling inputs are, optionally, implementedby event sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivesurface 604, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub-event, such as selection of an object on a user interface.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: at a device with one or moreprocessors, non-transitory memory, a display, and one or more inputdevices: detecting, via the one or more input devices, a first inputthat corresponds to selection of a collaboration affordance; and inresponse to detecting the selection of the collaboration affordance,displaying, on the display, a collaboration interface, includingconcurrently displaying: a first region that includes a plurality ofrepresentations of a plurality of content items that includes one ormore content items that are not jointly accessible by other users; and asecond region that includes a plurality of representations of aplurality of jointly accessible content items that are jointlyaccessible by the other users.
 2. The method of claim 1, whereindisplaying the collaboration interface includes concurrently displayinga tags region that includes a plurality of tags associated with theplurality of content items and the plurality of jointly accessiblecontent items.
 3. The method of claim 2, further comprising: detecting,via the one or more input devices, a second input that corresponds toselection of a respective tag among the plurality of tags in the tagsregion; and in response to detecting the selection of the respectivetag: updating the first region to include a subset of the plurality ofrepresentations of the plurality of content items that is associatedwith the respective tag; and updating the second region to include asubset of the plurality of representations of the plurality of jointlyaccessible content items that is associated with the respective tag. 4.The method of claim 2, further comprising: detecting, via the one ormore input devices, a second input that corresponds to selection of arespective tag among the plurality of tags in the tags region; and inresponse to detecting the selection of the respective tag, replacingdisplay of the collaboration interface with a projects interface thatincludes a third region associated with the respective tag with aplurality of representations of content items associated with therespective tag.
 5. The method of claim 4, wherein the projects interfacefurther includes a fourth region associated with a different tag with aplurality of representations of content items associated with thedifferent tag.
 6. The method of claim 1, wherein displaying thecollaboration interface includes concurrently displaying a collaboratorsregion that includes a plurality of representations of a plurality ofcollaborators associated with the plurality of content items and theplurality of jointly accessible content items.
 7. The method of claim 6,further comprising: detecting, via the one or more input devices, athird input that corresponds to selection of a respective representationcorresponding to a respective collaborator among the plurality ofrepresentations of the plurality of collaborators; and in response todetecting the selection of the respective representation correspondingto the respective collaborator: updating the first region to include asubset of the plurality of representations of the plurality of contentitems that is associated with the respective collaborator; and updatingthe second region to include a subset of the plurality ofrepresentations of the plurality of jointly accessible content itemsthat is associated with the respective collaborator.
 8. The method ofclaim 6, further comprising: detecting, via the one or more inputdevices, a third input that corresponds to selection of a respectiverepresentation corresponding to a respective collaborator among theplurality of representations of the plurality of collaborators; and inresponse to detecting the selection of the respective representationcorresponding to the respective collaborator, displaying, on thedisplay, a user information interface that includes informationassociated with the respective collaborator.
 9. The method of claim 1,wherein displaying the collaboration interface includes concurrentlydisplaying a locations region that includes a plurality ofrepresentations of a plurality of locations associated with theplurality of content items in addition to the first region and thesecond region.
 10. The method of claim 1, wherein metadata is displayedproximate to each of the plurality of representations of the pluralityof jointly accessible content items indicating recent activityassociated with a respective shared content item.
 11. The method ofclaim 1, further comprising: detecting, via the one or more inputdevices, a fourth input that corresponds to navigating within thecollaboration interface; and in response to detecting the fourth input:in accordance with a determination that the fourth input corresponds toa first input type, scrolling a portion of at least one of the firstregion or the collaborative-items region substantially horizontally; andin accordance with a determination that the fourth input corresponds toa second input type, scrolling a portion of the collaboration interfacesubstantially vertically.
 12. The method of claim 1, wherein the firstregion includes a first affordance provided to display additionalrepresentations of the plurality of recently modified content items whenselected, and wherein the collaborative-items region includes a secondaffordance provided to display additional representations of theplurality of jointly accessible content items.
 13. The method of claim1, further comprising: detecting, via the one or more input devices, afifth input that corresponds to selection of a respective representationfrom among the plurality of representations in the first region or theplurality of representations in the second region; and in response todetecting the selection of the respective representation, and inaccordance with a determination that the fifth input satisfies a contentpreview criterion, displaying, on the display a preview of a contentitem associated with the respective representation.
 14. The method ofclaim 13, further comprising: in response to detecting the selection ofthe respective representation, and in accordance with a determinationthat the fifth input satisfies an application launch criterion:launching an application that corresponds to the content item associatedwith the respective representation; and replacing display of thecollaboration interface with an interface associated with theapplication that includes the content item associated with therespective representation.
 15. The method of claim 1, wherein theplurality of content items corresponds to content items aggregated fromat least one of: one or more storage location, or one or more differentapplication, and wherein the plurality of jointly accessible contentitems corresponds to jointly accessible content items aggregated from atleast one of: two or more storage locations, or two or more differentstorage services.
 16. An electronic device, comprising: a display; oneor more input devices; one or more processors; non-transitory memory;and one or more programs, wherein the one or more programs are stored inthe non-transitory memory and configured to be executed by the one ormore processors, the one or more programs including instructions for:detecting, via the one or more input devices, a first input thatcorresponds to selection of a collaboration affordance; and in responseto detecting the selection of the collaboration affordance, displaying,on the display, a collaboration interface, including concurrentlydisplaying: a first region that includes a plurality of representationsof a plurality of content items that includes one or more content itemsthat are not jointly accessible by other users; and a second region thatincludes a plurality of representations of a plurality of jointlyaccessible content items that are jointly accessible by the other users.17. The electronic device of claim 16, wherein displaying thecollaboration interface includes concurrently displaying a tags regionthat includes a plurality of tags associated with the plurality ofcontent items and the plurality of jointly accessible content items. 18.The electronic device of claim 17, wherein the one or more programsinclude instructions for: detecting, via the one or more input devices,a second input that corresponds to selection of a respective tag amongthe plurality of tags in the tags region; and in response to detectingthe selection of the respective tag: updating the first region toinclude a subset of the plurality of representations of the plurality ofcontent items that is associated with the respective tag; and updatingthe second region to include a subset of the plurality ofrepresentations of the plurality of jointly accessible content itemsthat is associated with the respective tag.
 19. The electronic device ofclaim 17, wherein the one or more programs include instructions for:detecting, via the one or more input devices, a second input thatcorresponds to selection of a respective tag among the plurality of tagsin the tags region; and in response to detecting the selection of therespective tag, replacing display of the collaboration interface with aprojects interface that includes a third region associated with therespective tag with a plurality of representations of content itemsassociated with the respective tag.
 20. A non-transitory computerreadable storage medium storing one or more programs, the one or moreprograms comprising instructions, which, when executed by an electronicdevice with a display, and one or more input devices, cause theelectronic device to: detect, via the one or more input devices, a firstinput that corresponds to selection of a collaboration affordance; andin response to detecting the selection of the collaboration affordance,display, on the display, a collaboration, interface, includingconcurrently displaying: a first region that includes a plurality ofrepresentations of a plurality of content items that includes one ormore content items that are not jointly accessible by other users; and asecond region that includes a plurality of representations of aplurality of jointly accessible content items that are jointlyaccessible by the other users.